From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Christoph Lameter <cl@linux.com>
Cc: "Luck, Tony" <tony.luck@intel.com>, Nick Piggin <npiggin@suse.de>,
linux-kernel@vger.kernel.org, randy.dunlap_ocs10g@oracle.com,
Andrew Morton <akpm@linux-foundation.org>,
Paul Mundt <lethal@linux-sh.org>,
iwamatsu.nobuhiro@renesas.com
Subject: Re: linux-next ia64 build problems in slqb
Date: Tue, 21 Apr 2009 21:25:31 +0300 [thread overview]
Message-ID: <84144f020904211125v68b98df4ke1c04bc29df65fda@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0904211034550.19969@qirst.com>
On Tue, Apr 21, 2009 at 1:08 AM, Luck, Tony <tony.luck@intel.com> wrote:
>> > The ia64 "allnoconfig" build ends up with the (possibly dubious) combination
>> > of .config options:
>> >
>> > CONFIG_SMP=n
>> > CONFIG_NUMA=y
>>
>> Yeah, I don't think the combination makes much sense and x86 doesn't
>> allow it. Can we fix that in ia64 Kconfig? That said, this seems to
>> come up with every architecture except x86, so if someone is kind
>> enough to send me a tested fix for slqb, I'll just go ahead and apply
>> it.
On Tue, Apr 21, 2009 at 5:35 PM, Christoph Lameter <cl@linux.com> wrote:
> Tony runs tests with this configuration. This is an established
> configuration and has been historically supported.
Interesting. What exactly is an UP NUMA machine? Anyway, I'm more than
happy to apply a tested patch to fix up SLQB. Nick?
next prev parent reply other threads:[~2009-04-21 18:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 22:08 linux-next ia64 build problems in slqb Luck, Tony
2009-04-20 23:42 ` Randy Dunlap
2009-04-20 23:59 ` Luck, Tony
2009-04-21 5:51 ` Pekka Enberg
2009-04-21 6:29 ` Paul Mundt
2009-04-21 14:35 ` Christoph Lameter
2009-04-21 18:25 ` Pekka Enberg [this message]
2009-04-21 18:45 ` Luck, Tony
2009-04-21 19:07 ` Pekka Enberg
2009-04-21 22:31 ` Luck, Tony
2009-04-22 7:02 ` Pekka J Enberg
2009-04-23 5:50 ` Paul Mundt
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=84144f020904211125v68b98df4ke1c04bc29df65fda@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iwamatsu.nobuhiro@renesas.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=randy.dunlap_ocs10g@oracle.com \
--cc=tony.luck@intel.com \
/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).