From: Matthew Wilcox <willy@debian.org>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: willy@debian.org, linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: [2.6 patch] fix arch/i386/pci/Makefile
Date: Fri, 25 Jun 2004 19:01:15 +0100 [thread overview]
Message-ID: <20040625180115.GC28162@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20040625001513.GB18303@fs.tum.de>
On Fri, Jun 25, 2004 at 02:15:14AM +0200, Adrian Bunk wrote:
> This problem occurs with
> CONFIG_ACPI_PCI=y && (CONFIG_X86_VISWS=y || CONFIG_X86_NUMAQ=y)
That combination certainly doesn't make sense. No VisWS or NUMAQ systems
have ACPI. How did you manage to turn this on given:
menu "ACPI (Advanced Configuration and Power Interface) Support"
depends on !X86_VISWS
depends on !IA64_HP_SIM
depends on IA64 || X86
If you apply the following patch, does it help?
--- drivers/acpi/Kconfig 30 Mar 2004 12:42:25 -0000 1.11
+++ drivers/acpi/Kconfig 25 Jun 2004 18:00:29 -0000
@@ -3,7 +3,7 @@
#
menu "ACPI (Advanced Configuration and Power Interface) Support"
- depends on !X86_VISWS
+ depends on !X86_VISWS && !X86_NUMAQ
depends on !IA64_HP_SIM
depends on IA64 || X86
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2004-06-25 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-25 0:15 [2.6 patch] fix arch/i386/pci/Makefile Adrian Bunk
2004-06-25 4:01 ` Andrew Morton
2004-06-25 22:04 ` Adrian Bunk
2004-06-25 18:01 ` Matthew Wilcox [this message]
2004-06-25 22:03 ` Adrian Bunk
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=20040625180115.GC28162@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=bunk@fs.tum.de \
--cc=greg@kroah.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 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.