From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: "'Andrew Morton'" <akpm@osdl.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: 2.6.7-mm2 build failure
Date: Thu, 24 Jun 2004 12:10:18 -0700 [thread overview]
Message-ID: <200406241908.i5OJ8rY20620@unix-os.sc.intel.com> (raw)
In-Reply-To: <20040624115640.5f01ce20.akpm@osdl.org>
> Begin forwarded message:
>
> Date: Thu, 24 Jun 2004 07:43:58 -0700
> From: "Martin J. Bligh" <mbligh@aracnet.com>
> To: Andrew Morton <akpm@osdl.org>
> Cc: linux-kernel <linux-kernel@vger.kernel.org>
> Subject: 2.6.7-mm2 build failure
>
>
> drivers/base/node.c: In function `node_read_meminfo':
> drivers/base/node.c:56: warning: implicit declaration of function
> `hugetlb_report_node_meminfo'
> drivers/built-in.o(.text+0x1f615): In function `node_read_meminfo':
> : undefined reference to `hugetlb_report_node_meminfo'
> make: *** [.tmp_vmlinux1] Error 1
>
> Hmmm. I wonder if anyone tested that patch ;-)
>
Sorry, missing a #include. Tested with/without hugetlb config'ed. Previous
patch was tested with hugetlb page configured.
diff -Nur linux-2.6.7.orig/drivers/base/node.c linux-2.6.7/drivers/base/node.c
--- linux-2.6.7.orig/drivers/base/node.c 2004-06-15 22:18:59.000000000 -0700
+++ linux-2.6.7/drivers/base/node.c 2004-06-24 12:01:48.000000000 -0700
@@ -7,6 +7,7 @@
#include <linux/init.h>
#include <linux/mm.h>
#include <linux/node.h>
+#include <linux/hugetlb.h>
#include <linux/cpumask.h>
#include <linux/topology.h>
next parent reply other threads:[~2004-06-24 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040624115640.5f01ce20.akpm@osdl.org>
2004-06-24 19:10 ` Chen, Kenneth W [this message]
2004-06-24 20:35 ` 2.6.7-mm2 build failure Martin J. Bligh
2004-06-24 14:43 Martin J. Bligh
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=200406241908.i5OJ8rY20620@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.