From: khlebnikov@openvz.org (Konstantin Khlebnikov)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: __enabled_CONFIG_NUMA undeclared
Date: Sat, 18 Feb 2012 00:38:47 +0400 [thread overview]
Message-ID: <4F3EBAD7.6090705@openvz.org> (raw)
In-Reply-To: <CAOMZO5CarXUJ1XVJMWCEt1AXvnE5Gvunou_8nydjLmPVkZERMA@mail.gmail.com>
Fabio Estevam wrote:
> Hi,
>
> Building today's linux-next for ARM:
>
> CC arch/arm/kernel/asm-offsets.s
> In file included from include/linux/mm.h:8:0,
> from arch/arm/kernel/asm-offsets.c:14:
> include/linux/gfp.h: In function 'gfp_zonelist':
> include/linux/gfp.h:267:1: error: '__enabled_CONFIG_NUMA' undeclared
> (first use in this function)
> include/linux/gfp.h:267:1: note: each undeclared identifier is
> reported only once for each function it appears in
> include/linux/gfp.h:267:1: error: '__enabled_CONFIG_NUMA_MODULE'
> undeclared (first use in this function)
> make[1]: *** [arch/arm/kernel/asm-offsets.s] Error 1
>
> , which is caused by commit 053361e1a (mm: replace NUMA_BUILD with
> IS_ENABLED(CONFIG_NUMA)
Thanks. Stephen Rothwell already reported about this bug.
see patch "mm: add config NUMA stub to all architectures"
prev parent reply other threads:[~2012-02-17 20:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 20:12 ARM: __enabled_CONFIG_NUMA undeclared Fabio Estevam
2012-02-17 20:27 ` richard -rw- weinberger
2012-02-17 20:38 ` Konstantin Khlebnikov [this message]
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=4F3EBAD7.6090705@openvz.org \
--to=khlebnikov@openvz.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).