From: Matthew Dobson <colpatch@us.ibm.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>,
Martin Bligh <mjbligh@us.ibm.com>,
Trivial Patch Monkey <trivial@rustcorp.com.au>
Subject: [patch] Remove sole CONFIG_MULIQUAD in kernel source
Date: Wed, 30 Oct 2002 16:14:42 -0800 [thread overview]
Message-ID: <3DC075F2.6070107@us.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 588 bytes --]
Linus,
There is one remaining instance of CONFIG_MULTIQUAD in the kernel source.
This hanger-on must go! It means that (since CONFIG_MULTIQUAD is no
longer defined) the NUMA-Q specific PCI code is no longer compiled in.
This is bad...
[mcd@arrakis linux-2.5.44-vanilla]$ grep -r CONFIG_MULTIQUAD *
arch/i386/pci/Makefile:ifdef
CONFIG_MULTIQUAD
arch/i386/pci/Makefile:endif
# CONFIG_MULTIQUAD
[mcd@arrakis patches]$ diffstat multiquad_fix/multiquad_pci_fix-2.5.44.patch
Makefile | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
Please apply...
Cheers!
-Matt
[-- Attachment #2: multiquad_pci_fix-2.5.44.patch --]
[-- Type: text/plain, Size: 648 bytes --]
diff -Nur --exclude-from=/usr/src/.dontdiff linux-2.5.39-multiquad/arch/i386/pci/Makefile linux-2.5.39-multiquad+numa_rename/arch/i386/pci/Makefile
--- linux-2.5.39-multiquad/arch/i386/pci/Makefile Fri Sep 27 14:50:18 2002
+++ linux-2.5.39-multiquad+numa_rename/arch/i386/pci/Makefile Mon Sep 30 11:21:09 2002
@@ -3,7 +3,7 @@
obj-$(CONFIG_PCI_BIOS) += pcbios.o
obj-$(CONFIG_PCI_DIRECT) += direct.o
-ifdef CONFIG_MULTIQUAD
+ifdef CONFIG_X86_NUMAQ
obj-y += numa.o
else
obj-y += fixup.o
@@ -14,7 +14,7 @@
obj-y += legacy.o
-endif # CONFIG_MULTIQUAD
+endif # CONFIG_X86_NUMAQ
obj-y += irq.o common.o
include $(TOPDIR)/Rules.make
reply other threads:[~2002-10-31 0:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3DC075F2.6070107@us.ibm.com \
--to=colpatch@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjbligh@us.ibm.com \
--cc=torvalds@transmeta.com \
--cc=trivial@rustcorp.com.au \
/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.