From: William Lee Irwin III <wli@holomorphy.com>
To: Andi Kleen <ak@suse.de>
Cc: john stultz <johnstul@us.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@digeo.com>,
"Martin J. Bligh" <mbligh@aracnet.com>,
keith maanthey <kmannth@us.ibm.com>
Subject: Re: [PATCH] linux-2.5.69_subarch-fix_A0.patch
Date: Thu, 15 May 2003 12:19:19 -0700 [thread overview]
Message-ID: <20030515191919.GR8978@holomorphy.com> (raw)
In-Reply-To: <20030515190006.GA30173@Wotan.suse.de>
On Thu, May 15, 2003 at 10:46:03AM -0700, john stultz wrote:
>> I'd agree (long term even more strongly), although along with that I'd
>> like to be able to pick and choose my subarch. So I can have a kernel
>> that supports say, PC and BigSMP, but not NUMAQ or whatever. I believe
>> this is doable with your infrastructure, but I'm not sure how much work
>> it will take.
On Thu, May 15, 2003 at 09:00:06PM +0200, Andi Kleen wrote:
> NUMAQ is not supported by the generic subarchitecture anyways.
> The only supported architecturs by generic are pc, bigsmp, summit.
> In theory you could subselect them, but it's only a few bytes for each
> so it's probably not worth the effort. Technically it isn't a big issue,
> you would just need to add it to Kconfig (not sure how to do that cleanly),
> the Makefile and the probe table.
Okay, will fix.
-- wli
next prev parent reply other threads:[~2003-05-15 19:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 2:37 john stultz
2003-05-15 6:51 ` Andi Kleen
2003-05-15 17:20 ` john stultz
2003-05-15 17:28 ` Andi Kleen
2003-05-15 17:46 ` john stultz
2003-05-15 19:00 ` Andi Kleen
2003-05-15 19:19 ` William Lee Irwin III [this message]
2003-05-15 17:17 ` Martin J. Bligh
2003-05-15 19:50 ` Andi Kleen
2003-05-15 19:55 ` William Lee Irwin III
2003-05-15 17:45 ` Martin J. Bligh
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=20030515191919.GR8978@holomorphy.com \
--to=wli@holomorphy.com \
--cc=ak@suse.de \
--cc=akpm@digeo.com \
--cc=johnstul@us.ibm.com \
--cc=kmannth@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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®