From: David Rientjes <rientjes@google.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>
Cc: kbuild test robot <fengguang.wu@intel.com>,
linux-mm@kvack.org, Johannes Weiner <hannes@cmpxchg.org>,
kbuild-all@01.org
Subject: [patch] kexec: export free_huge_page to VMCOREINFO fix
Date: Wed, 30 Jul 2014 17:30:28 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1407301727300.12181@chino.kir.corp.google.com> (raw)
In-Reply-To: <53d98399.wRC4T5IRh+/QWqVO%fengguang.wu@intel.com>
free_huge_page() is undefined without CONFIG_HUGETLBFS and there's no need
to filter PageHuge() page is such a configuration either.
Reported-by: kbuild test robot <fengguang.wu@intel.com>
Signed-off-by: David Rientjes <rientjes@google.com>
---
To be folded into kexec-export-free_huge_page-to-vmcoreinfo.patch.
kernel/kexec.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/kernel/kexec.c b/kernel/kexec.c
--- a/kernel/kexec.c
+++ b/kernel/kexec.c
@@ -1994,7 +1994,9 @@ static int __init crash_save_vmcoreinfo_init(void)
#endif
VMCOREINFO_NUMBER(PG_head_mask);
VMCOREINFO_NUMBER(PAGE_BUDDY_MAPCOUNT_VALUE);
+#ifdef CONFIG_HUGETLBFS
VMCOREINFO_SYMBOL(free_huge_page);
+#endif
arch_crash_save_vmcoreinfo();
update_vmcoreinfo_note();
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-07-31 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 23:45 [mmotm:master 16/573] kernel/kexec.c:1623:20: error: 'free_huge_page' undeclared kbuild test robot
2014-07-31 0:30 ` David Rientjes [this message]
2014-07-31 1:20 ` [patch] kexec: export free_huge_page to VMCOREINFO fix Olof Johansson
2014-07-31 2:01 ` David Rientjes
2014-07-31 2:05 ` [patch for-3.16] kexec: fix build error when hugetlbfs is disabled David Rientjes
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=alpine.DEB.2.02.1407301727300.12181@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
--cc=linux-mm@kvack.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