All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] remove CONFIG_X86_NUMA
Date: Sun, 29 Dec 2002 23:04:19 +0100	[thread overview]
Message-ID: <20021229230419.A12194@lst.de> (raw)

It's only used to hide two entries in arch/i386/Kconfig.

ACKed my mbligh.


--- 1.14/arch/i386/Kconfig	Tue Dec 17 19:50:36 2002
+++ edited/arch/i386/Kconfig	Sat Dec 21 18:10:12 2002
@@ -385,14 +385,8 @@
 	  This is purely to save memory - each supported CPU adds
 	  approximately eight kilobytes to the kernel image.
 
-config X86_NUMA
-	bool "Multi-node NUMA system support"
-	depends on SMP
-
-#Platform Choices
 config X86_NUMAQ
 	bool "Multiquad (IBM/Sequent) NUMAQ support"
-	depends on X86_NUMA
 	help
 	  This option is used for getting Linux to run on a (IBM/Sequent) NUMA 
 	  multiquad box. This changes the way that processors are bootstrapped,
@@ -402,7 +396,6 @@
 
 config X86_SUMMIT
 	bool "IBM x440 (Summit/EXA) support"
-	depends on X86_NUMA
 	help
 	  This option is needed for IBM systems that use the Summit/EXA chipset.
 	  In particular, it is needed for the x440.
@@ -411,7 +404,7 @@
 
 config CLUSTERED_APIC
 	bool
-	depends on X86_NUMA && (X86_NUMAQ || X86_SUMMIT)
+	depends on X86_NUMAQ || X86_SUMMIT
 	default y
 
 # Common NUMA Features

             reply	other threads:[~2002-12-29 21:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-29 22:04 Christoph Hellwig [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-29 22:39 [PATCH] remove CONFIG_X86_NUMA James Bottomley
2002-12-29 22:40 ` Christoph Hellwig
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

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=20021229230419.A12194@lst.de \
    --to=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.