Kyle Moffett <[email protected]> writes:
> This is
> _exactly_ the way things work now, except there is no outside llh
> project, it's all stored in the kernel tree.
Precisely. I also think we don't have to worry about namespace
contamination and non-compliance to random "standards". It is the
userland _using_ the kernel headers at its discretion, we don't force
anyone to include anything. If something includes, say, kabi/hdlc.h
(just to make sure I know the details) then it has to be prepared
for hdlc_device struct to be defined, even if System 5 3/4 R 1.2.3.4
says nothing about it.
If glibc (as opposed to kernel utils) wants to use the kabi headers
(and I presume it should) then it has to build its own files based
on ours and/or should do other necessary steps to prevent namespace
problems (such as carefully picking files to include instead of
#include <kabi/*>). It will be easier than now anyway and I think
we're all open for suggestions.
If it turns out that we need a separate kabi/*.h file for every kernel
API structure or a set of #defines then let it be.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
