On Mon, Sep 21, 2009 at 04:37:12PM +0200, Arnd Bergmann wrote: > User applications frequently hit problems when they try to use > the kernel headers directly, rather than the exported headers. > > This adds an explicit warning for this case, and points to > a URL holding an explanation of why this is wrong and what > to do about it. Like the idea. > > Signed-off-by: Arnd Bergmann <arnd@xxxxxxxx> > --- > include/linux/kernel.h | 6 ++++++ > scripts/headers_install.pl | 2 +- > 2 files changed, 7 insertions(+), 1 deletion(-) > > diff --git a/include/linux/kernel.h b/include/linux/kernel.h > index d6320a3..f392d72 100644 > --- a/include/linux/kernel.h > +++ b/include/linux/kernel.h > @@ -656,6 +656,12 @@ extern int do_sysinfo(struct sysinfo *info); > > #endif /* __KERNEL__ */ > > +#ifndef __EXPORTED_HEADERS__ But why do we need this "__EXPORTED_HEADERS__" thing? ? Sam -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
