From: akpm-3NddpPZAyC0@public.gmane.org
To: len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
akpm-3NddpPZAyC0@public.gmane.org,
bunk-HeJ8Db2Gnd6zQB+pC5nmwQ@public.gmane.org
Subject: [patch 5/9] ACPI should depend on, not select PCI
Date: Fri, 28 Oct 2005 14:59:50 -0700 [thread overview]
Message-ID: <200510282159.j9SLxWD9021616@shell0.pdx.osdl.net> (raw)
From: Adrian Bunk <bunk-HeJ8Db2Gnd6zQB+pC5nmwQ@public.gmane.org>
ACPI should depend on, not select PCI.
The practical differences should be nearly zero except that it avoids
the illegal configuration PCI=y, X86_VOYAGER=y.
Signed-off-by: Adrian Bunk <bunk-HeJ8Db2Gnd6zQB+pC5nmwQ@public.gmane.org>
Signed-off-by: Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>
---
drivers/acpi/Kconfig | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/acpi/Kconfig~acpi-should-depend-on-not-select-pci drivers/acpi/Kconfig
--- 25/drivers/acpi/Kconfig~acpi-should-depend-on-not-select-pci Fri Oct 28 14:59:08 2005
+++ 25-akpm/drivers/acpi/Kconfig Fri Oct 28 14:59:21 2005
@@ -10,8 +10,8 @@ menu "ACPI (Advanced Configuration and P
config ACPI
bool "ACPI Support"
depends on IA64 || X86
+ depends on PCI
select PM
- select PCI
default y
---help---
_
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
next reply other threads:[~2005-10-28 21:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 21:59 akpm-3NddpPZAyC0 [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-01 1:58 [patch 5/9] ACPI should depend on, not select PCI Brown, Len
2005-12-01 10:00 ` Roman Zippel
2005-12-04 16:09 ` 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=200510282159.j9SLxWD9021616@shell0.pdx.osdl.net \
--to=akpm-3nddppzayc0@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=bunk-HeJ8Db2Gnd6zQB+pC5nmwQ@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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