From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Richard Weinberger <richard@nod.at>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: linux-next: Tree for Feb 17 (uml)
Date: Fri, 17 Feb 2012 10:34:48 -0800 [thread overview]
Message-ID: <4F3E9DC8.6090304@xenotime.net> (raw)
In-Reply-To: <20120217165045.2394d944d6efc37104421d2e@canb.auug.org.au>
On 02/16/2012 09:50 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20120216:
uml on x86_64 (defconfig):
CC arch/um/kernel/asm-offsets.s
In file included from linux-next-20120217/include/linux/slab.h:12:0,
from linux-next-20120217/include/linux/crypto.h:23,
from
linux-next-20120217/arch/x86/um/shared/sysdep/kernel-offsets.h:4,
from linux-next-20120217/arch/um/kernel/asm-offsets.c:1:
linux-next-20120217/include/linux/gfp.h: In function 'gfp_zonelist':
linux-next-20120217/include/linux/gfp.h:267:1: error:
'__enabled_CONFIG_NUMA' undeclared (first use in this function)
linux-next-20120217/include/linux/gfp.h:267:1: note: each undeclared
identifier is reported only once for each function it appears in
linux-next-20120217/include/linux/gfp.h:267:1: error:
'__enabled_CONFIG_NUMA_MODULE' undeclared (first use in this function)
--
~Randy
next prev parent reply other threads:[~2012-02-17 18:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 5:50 linux-next: Tree for Feb 17 Stephen Rothwell
2012-02-17 18:00 ` linux-next: Tree for Feb 17 (kernel/kcmp.c) Randy Dunlap
2012-02-17 23:14 ` Stephen Rothwell
2012-02-18 6:58 ` Cyrill Gorcunov
2012-02-22 20:20 ` Randy Dunlap
2012-02-22 20:29 ` Cyrill Gorcunov
2012-02-17 18:34 ` Randy Dunlap [this message]
2012-02-17 21:32 ` linux-next: Tree for Feb 17 (uml) Geert Uytterhoeven
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=4F3E9DC8.6090304@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=richard@nod.at \
--cc=sfr@canb.auug.org.au \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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).