mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Pekka Enberg <penberg@cs.helsinki.fi>
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>,
	Christoph Lameter <cl@linux-foundation.org>
Subject: Re: linux-next ia64 build problems in slqb
Date: Tue, 21 Apr 2009 15:29:53 +0900	[thread overview]
Message-ID: <20090421062952.GA15167@linux-sh.org> (raw)
In-Reply-To: <84144f020904202251n616f188k80c6ce7d974d8b00@mail.gmail.com>

On Tue, Apr 21, 2009 at 08:51:47AM +0300, Pekka Enberg wrote:
> Hi Tony,
> 
> 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.
> 
This configuration is used on SH quite regularly, so if SLQB breaks, then
that is a regression.

  reply	other threads:[~2009-04-21  6:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20 22:08 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 [this message]
2009-04-21 14:35   ` Christoph Lameter
2009-04-21 18:25     ` Pekka Enberg
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=20090421062952.GA15167@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    --cc=penberg@cs.helsinki.fi \
    --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

all inboxes | Powered by JetHome®