i'm curious about the fact that a small number of header files that are exported to user space have preprocessor checks for *not* defined __KERNEL__, as in: linux/acct.h:#if !defined(CONFIG_M68K) || !defined(__KERNEL__) video/edid.h:#if !defined(__KERNEL__) || defined(CONFIG_X86) it's obvious that the purpose of the check "#ifdef __KERNEL__" is to prevent some header file content from being exposed to user space. but to check for the opposite just strikes me as kind of weird -- it's saying that there's some content that *shouldn't* be in kernel space, but should be available in user space, and i don't see why the kernel should be defining that kind of content. any rationale for this sort of thing? thanks. rday ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA http://crashcourse.ca ======================================================================== -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
