From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [tip:master 30/35] mm/memory.c:72:2: warning: #warning Unfortunate NUMA config, growing page-frame f
Date: Fri, 28 Sep 2012 09:55:26 +0000 [thread overview]
Message-ID: <20120928095526.GA28747@localhost> (raw)
Hi Peter,
FYI, there are new compile warnings show up in
tree: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master
head: 2ef756a2e79149dc84c88f7ccc42ec38cbb7722e
commit: 835e3cf29f4eeba6c5c8bcc188b2138029157938 [30/35] mm: Fold page::nid_last into page::flags when possible
config: i386-allmodconfig
All warnings:
mm/memory.c:72:2: warning: #warning Unfortunate NUMA config, growing page-frame for last_nid. [-Wcpp]
vim +72 mm/memory.c
42b77728 (Jan Beulich 2008-07-23 69) #include "internal.h"
42b77728 (Jan Beulich 2008-07-23 70)
835e3cf2 (Peter Zijlstra 2012-08-13 71) #ifdef LAST_NID_NOT_IN_PAGE_FLAGS
835e3cf2 (Peter Zijlstra 2012-08-13 @72) #warning Unfortunate NUMA config, growing page-frame for last_nid.
835e3cf2 (Peter Zijlstra 2012-08-13 73) #endif
835e3cf2 (Peter Zijlstra 2012-08-13 74)
d41dee36 (Andy Whitcroft 2005-06-23 75) #ifndef CONFIG_NEED_MULTIPLE_NODES
^1da177e (Linus Torvalds 2005-04-16 76) /* use the per-pgdat data instead for discontigmem - mbligh */
^1da177e (Linus Torvalds 2005-04-16 77) unsigned long max_mapnr;
^1da177e (Linus Torvalds 2005-04-16 78) struct page *mem_map;
^1da177e (Linus Torvalds 2005-04-16 79)
^1da177e (Linus Torvalds 2005-04-16 80) EXPORT_SYMBOL(max_mapnr);
---
0-DAY kernel build testing backend Open Source Technology Centre
Fengguang Wu, Yuanhan Liu Intel Corporation
next reply other threads:[~2012-09-28 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 9:55 Fengguang Wu [this message]
2012-09-28 10:25 ` [tip:master 30/35] mm/memory.c:72:2: warning: #warning Unfortunate NUMA config, growing page-fra Peter Zijlstra
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=20120928095526.GA28747@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@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.