From: "Sachin P. Sant" <sachinp@in.ibm.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
LKML <linux-kernel@vger.kernel.org>,
linuxppc-dev@ozlabs.org, Pekka Enberg <penberg@cs.helsinki.fi>,
linux-next@vger.kernel.org
Subject: Re: next Feb 10: mm/slqb build break
Date: Thu, 12 Feb 2009 16:58:37 +0530 [thread overview]
Message-ID: <499407E5.1070705@in.ibm.com> (raw)
In-Reply-To: <20090212014503.GD30043@wotan.suse.de>
Nick Piggin 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...
I am not sure if this is a valid config. According to arch/powerpc/Kconfig
NUMA depends on PPC64 and defaults to y if SMP & PPC_PSERIES is set.
If this is not a valid config then may be the make randconfig rules
need to be changed accordingly.
Ben should know. Ben ??
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
prev parent reply other threads:[~2009-02-12 11:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090210194121.80256b72.sfr@canb.auug.org.au>
[not found] ` <49914790.6050008@in.ibm.com>
[not found] ` <49914EE7.7030205@in.ibm.com>
2009-02-10 11:53 ` next Feb 10: mm/slqb build break Pekka Enberg
2009-02-12 1:45 ` Nick Piggin
2009-02-12 1:47 ` David Miller
2009-02-12 11:28 ` Sachin P. Sant [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=499407E5.1070705@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=npiggin@suse.de \
--cc=penberg@cs.helsinki.fi \
--cc=sfr@canb.auug.org.au \
/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).