From: David Miller <davem@davemloft•net>
To: npiggin@suse•de
Cc: penberg@cs•helsinki.fi, sachinp@in•ibm.com, sfr@canb•auug.org.au,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
linuxppc-dev@ozlabs•org
Subject: Re: next Feb 10: mm/slqb build break
Date: Wed, 11 Feb 2009 17:47:33 -0800 (PST) [thread overview]
Message-ID: <20090211.174733.163367216.davem@davemloft.net> (raw)
In-Reply-To: <20090212014503.GD30043@wotan.suse.de>
From: Nick Piggin <npiggin@suse•de>
Date: Thu, 12 Feb 2009 02:45:03 +0100
> On Tue, Feb 10, 2009 at 01:53:51PM +0200, Pekka Enberg wrote:
> > Actually, that's not the root cause here. You seem to have CONFIG_SMP
> > disabled but CONFIG_NUMA enabled. That's not possible on x86 which
> > makes me think it's a ppc kconfig bug. Hmm?
>
> If it is really a valid config, then we should be able to make
> slqb build with it...
FWIW I only allow NUMA with SMP on sparc64, just like x86.
Although it seems IA64, like powerpc, does not have this restriction.
Hmmm...
next prev parent reply other threads:[~2009-02-12 1:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 8:41 linux-next: Tree for February 10 Stephen Rothwell
2009-02-10 9:23 ` next Feb 10: mm/slqb build break Sachin P. Sant
2009-02-10 9:54 ` Sachin P. Sant
2009-02-10 11:53 ` Pekka Enberg
2009-02-12 1:45 ` Nick Piggin
2009-02-12 1:47 ` David Miller [this message]
2009-02-12 11:28 ` Sachin P. Sant
2009-02-12 11:28 ` Sachin P. Sant
2009-02-12 11:28 ` Sachin P. Sant
2009-02-10 10:30 ` Next Feb 10 : build/break arch/s390kernel.irq.o Sachin P. Sant
2009-02-10 11:15 ` [Patch] [s390] Fix init irq proc build break Sachin P. Sant
2009-02-10 11:40 ` Martin Schwidefsky
2009-02-10 10:45 ` Next Feb 10 build break on s390 : mm/shmem.c Sachin P. Sant
2009-02-10 13:40 ` Mimi Zohar
2009-02-10 19:55 ` linux-next: Tree for February 10 (security/audit/ima) Randy Dunlap
2009-02-10 22:40 ` Stephen Rothwell
2009-02-11 0:30 ` Mimi Zohar
2009-02-12 17:54 ` [PATCH -next] security/audit/ima: fix build error Randy Dunlap
2009-02-12 18:24 ` Mimi Zohar
2009-02-12 18:30 ` Randy Dunlap
2009-02-12 22:31 ` James Morris
2009-02-11 1:29 ` linux-next: Tree for February 10 (security/audit/ima) Al Viro
2009-02-11 2:27 ` Stephen Rothwell
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=20090211.174733.163367216.davem@davemloft.net \
--to=davem@davemloft$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=npiggin@suse$(echo .)de \
--cc=penberg@cs$(echo .)helsinki.fi \
--cc=sachinp@in$(echo .)ibm.com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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