From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Chris Clayton <chris2553@googlemail.com>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Mel Gorman <mel@csn.ul.ie>
Subject: [PATCH] hugetlbfs: fix build failure with !CONFIG_HUGETLBFS
Date: Tue, 10 Feb 2009 23:27:32 +0100 (CET) [thread overview]
Message-ID: <tkrat.a79dcd647f8ae43e@s5r6.in-berlin.de> (raw)
In-Reply-To: <c6b1100b0902101353q2c5ad750t2a901de97dc5fe5@mail.gmail.com>
Fix regression due to 5a6fe125950676015f5108fb71b2a67441755003,
"Do not account for the address space used by hugetlbfs using VM_ACCOUNT"
which added an argument to the function hugetlb_file_setup() but not to
the macro hugetlb_file_setup().
Reported-by: Chris Clayton <chris2553@googlemail.com>
Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
---
include/linux/hugetlb.h | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/linux/hugetlb.h b/include/linux/hugetlb.h
index af09660..03be7f2 100644
--- a/include/linux/hugetlb.h
+++ b/include/linux/hugetlb.h
@@ -159,9 +159,9 @@ static inline void set_file_hugepages(struct file *file)
}
#else /* !CONFIG_HUGETLBFS */
-#define is_file_hugepages(file) 0
-#define set_file_hugepages(file) BUG()
-#define hugetlb_file_setup(name,size) ERR_PTR(-ENOSYS)
+#define is_file_hugepages(file) 0
+#define set_file_hugepages(file) BUG()
+#define hugetlb_file_setup(name,size,acctflag) ERR_PTR(-ENOSYS)
#endif /* !CONFIG_HUGETLBFS */
--
1.6.0.6
--
Stefan Richter
-=====-==--= --=- -=-=-
http://arcgraph.de/sr/
next prev parent reply other threads:[~2009-02-10 22:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 21:53 2.6.29-rc4-git2 build failure Chris Clayton
2009-02-10 22:27 ` Stefan Richter [this message]
2009-02-10 22:44 ` [PATCH] hugetlbfs: fix build failure with !CONFIG_HUGETLBFS Mel Gorman
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=tkrat.a79dcd647f8ae43e@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=chris2553@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=torvalds@linux-foundation.org \
/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®