From: Pekka Enberg <penberg@cs.helsinki.fi>
To: mingo@elte.hu
Cc: eduard.munteanu@linux360.ro, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] kmemtrace: fix build brekage in linux/fs.h
Date: Tue, 24 Mar 2009 10:14:32 +0200 [thread overview]
Message-ID: <1237882472.25315.32.camel@penberg-laptop> (raw)
From: Pekka Enberg <penberg@cs.helsinki.fi>
Impact: fix build
This patch fixes up the following build breakage caused by commit
e251ea2fa52321009940fad02238ef1c369531ae ("rcu: don't include unnecessary
headers, allow kmemtrace w/ tracepoints").
CC init/do_mounts_initrd.o
In file included from init/do_mounts_initrd.c:3:
include/linux/fs.h: In function ‘alloc_secdata’:
include/linux/fs.h:2237: error: implicit declaration of function ‘get_zeroed_page’
include/linux/fs.h:2237: error: ‘GFP_KERNEL’ undeclared (first use in this function)
include/linux/fs.h:2237: error: (Each undeclared identifier is reported only once
include/linux/fs.h:2237: error: for each function it appears in.)
include/linux/fs.h: In function ‘free_secdata’:
include/linux/fs.h:2242: error: implicit declaration of function ‘free_page’
In file included from include/linux/slab.h:12,
from include/linux/percpu.h:5,
from include/linux/percpu_counter.h:13,
from include/linux/ext2_fs_sb.h:20,
from include/linux/ext2_fs.h:69,
from init/do_mounts_initrd.c:5:
include/linux/gfp.h: At top level:
include/linux/gfp.h:223: error: conflicting types for ‘get_zeroed_page’
include/linux/fs.h:2237: error: previous implicit declaration of ‘get_zeroed_page’ was here
make[1]: *** [init/do_mounts_initrd.o] Error 1
make: *** [init] Error 2
Cc: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi>
---
include/linux/fs.h | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/include/linux/fs.h b/include/linux/fs.h
index 92734c0..add95da 100644
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -8,6 +8,7 @@
#include <linux/limits.h>
#include <linux/ioctl.h>
+#include <linux/gfp.h>
/*
* It's silly to have NR_OPEN bigger than NR_FILE, but you can change
--
1.5.4.3
reply other threads:[~2009-03-24 8:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1237882472.25315.32.camel@penberg-laptop \
--to=penberg@cs.helsinki.fi \
--cc=eduard.munteanu@linux360.ro \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®