| From | David Howells <> | Subject | Re: [RFC] Splitting kernel headers and deprecating __KERNEL__ | Date | Mon, 29 Nov 2004 11:08:34 +0000 |
| |
Grzegorz Kulewski <kangur@polcom.net>: > > (b) Make kernel file #include the user file. > > Does kernel really need to include user headers? When it is definition of > some const then it should be defined in one file (to be sure it has only > one definition). But user headers may have some compatibility hacks that > kernel do not need (and even maybe does not want) to have. > > How you will handle that?
I must have mis-explained it. I meant:
> > (b) Make kernel file #include the user/ file.
I don't actually mean that the kernel should in anyway touch userspace headers. I was referring to the bits split out into user-xxxx/ directories.
David - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|