Daniel Jacobowitz wrote: > I would really like to come up with an approach to maintain this interface > definition in the kernel source. I'm still trying to think of a > way to do it without breaking compatibility or kernel builds. 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. This sounds too easy though--I'm sure I've missed something, but I can't think what.... 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 availableChris Friesen
- Userland headers availableMariusz Mazur
- Re: Userland headers availableDaniel Jacobowitz
- Prev by Date: Linux 2.4.25-pre7
- Next by Date: Re: 2.6.2-rc1-mm2
- Previous by thread: Re: Userland headers available
- Next by thread: Re: Userland headers available
- Indexes:[Main][Thread]