From: Christoph Hellwig <hch@lst.de>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: hch@lst.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remove CONFIG_X86_NUMA
Date: Sun, 29 Dec 2002 23:40:51 +0100 [thread overview]
Message-ID: <20021229234051.A12535@lst.de> (raw)
In-Reply-To: <200212292239.gBTMdPJ12407@localhost.localdomain>; from James.Bottomley@steeleye.com on Sun, Dec 29, 2002 at 04:39:25PM -0600
On Sun, Dec 29, 2002 at 04:39:25PM -0600, James Bottomley wrote:
> > It's only used to hide two entries in arch/i386/Kconfig.
>
> The patch looks good. If it's OK to get rid of X86_NUMA, could you also move
> X86_NUMAQ under the subarch menu?
I already wondered about that, but AFAIK a kernel with X86_NUMAQ set
still boots on a PeeCee, so it's really an option, not a choice.
next prev parent reply other threads:[~2002-12-29 22:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-29 22:39 [PATCH] remove CONFIG_X86_NUMA James Bottomley
2002-12-29 22:40 ` Christoph Hellwig [this message]
2002-12-29 22:51 ` James Bottomley
2002-12-29 22:58 ` Christoph Hellwig
2002-12-29 23:06 ` James Bottomley
2002-12-29 22:56 ` Martin J. Bligh
2002-12-29 23:42 ` William Lee Irwin III
-- strict thread matches above, loose matches on Subject: below --
2002-12-29 22:04 Christoph Hellwig
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=20021229234051.A12535@lst.de \
--to=hch@lst.de \
--cc=James.Bottomley@steeleye.com \
--cc=linux-kernel@vger.kernel.org \
/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