Friesen, Christopher [CAR:7Q28:EXCH] wrote: > The obvious way is to have the kernel headers include the userland > headers, then everything below that be wrapped in "#ifdef __KERNEL__". > Userland then includes the normal kernel headers, but only gets the > userland-safe ones. I just realized this wasn't clear. I envision a new set of headers in the kernel that are clean to export to userland. The current headers then include the appropriate userland-clean ones, and everything below that is kernel only. This lets the kernel maintain the userland-clean headers explicitly, and we don't have the work of cleaning them up for glibc. Chris -- Chris Friesen | MailStop: 043/33/F10 Nortel Networks | work: (613) 765-0557 3500 Carling Avenue | fax: (613) 765-2986 Nepean, ON K2H 8E9 Canada | email: cfriesen _at_ nortelnetworks.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- Re: Userland headers availablejw schultz
- Re: Userland headers availableH. Peter Anvin
- Userland headers availableMariusz Mazur
- Re: Userland headers availableDaniel Jacobowitz
- Re: Userland headers availableChris Friesen
- Prev by Date: Re: [patch] PCI Express Enhanced Config Patch - 2.6.0-test11
- Next by Date: Re: 2.6.1 "clock preempt"?
- Previous by thread: Re: Userland headers available
- Next by thread: Re: Userland headers available
- Indexes:[Main][Thread]