Horst von Brand wrote:
I am contacting you to express my concern over a growing trend in kernel
development. I am specifically referring to changes being made to kernel
headers that break compatibility at the userland level, where __KERNEL__
isn't #define'd.
The policy with respect to kernel headers is /very/ simple:
T H E Y A R E N E V E R U S E D F R O M U S E R L A N D.
This general policy makes all your points (trivially) moot.
I must admit a little confusion here. Clearly, kernel header files are
used at the user level. The kernel and user level applications must share
definitions for a great many things.
Perhaps more precisely, the rule is that kernel header files should not be
#include'd directly from user level applications, but may be #include'd
indirectly through other header files as appropriate?
Thanx...
ps
-
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]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |