From: Arnd Bergmann <arnd@arndb.de>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: mingo@elte.hu, eduard.munteanu@linux360.ro, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] fs: don't include <linux/gfp.h> to fix headers-export-check
Date: Tue, 24 Mar 2009 14:12:09 +0100 [thread overview]
Message-ID: <200903241412.09730.arnd@arndb.de> (raw)
In-Reply-To: <1237888763.25315.70.camel@penberg-laptop>
On Tuesday 24 March 2009, Pekka Enberg wrote:
>
> From: Pekka Enberg <penberg@cs.helsinki.fi>
>
> Impact: fix build
>
> This patch fixes a headers-export-check failure:
>
> /home/mingo/tip/usr/include/linux/bsg.h:11: found __[us]{8,16,32,64} type without #include <linux/types.h>
> /home/mingo/tip/usr/include/linux/fs.h:11: included file 'linux/gfp.h' is not exported
> make[3]: *** [/home/mingo/tip/usr/include/linux/.check] Error 1
> make[2]: *** [linux] Error 2
>
> Cc: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
> Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi>
> ---
> include/linux/fs.h | 16 ++++++----------
> 1 files changed, 6 insertions(+), 10 deletions(-)
>
> diff --git a/include/linux/fs.h b/include/linux/fs.h
> index add95da..11fdc57 100644
> --- a/include/linux/fs.h
> +++ b/include/linux/fs.h
> @@ -8,7 +8,6 @@
>
> #include <linux/limits.h>
> #include <linux/ioctl.h>
> -#include <linux/gfp.h>
>
> /*
I think a cleaner fix would be to move the include of gfp.h into the
second #include block that is part of #ifdef __KERNEL__, as is the
only user of get_zeroed_page in there.
Arnd <><
next prev parent reply other threads:[~2009-03-24 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 9:59 Pekka Enberg
2009-03-24 10:06 ` [tip:tracing/kmemtrace] " Pekka Enberg
2009-03-24 13:12 ` Arnd Bergmann [this message]
2009-03-24 13:14 ` [PATCH 2/2] " Pekka Enberg
2009-03-24 13:17 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200903241412.09730.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=eduard.munteanu@linux360.ro \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®