From: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
To: Keshavamurthy Anil S <anil.s.keshavamurthy@intel.com>
Cc: linux-acpi@vger.kernel.org, len.brown@intel.com, akpm@osdl.org,
zippel@linux-m68k.org, rdunlap@xenotime.net,
linux-kernel@vger.kernel.org, greg@kroah.com,
pcihpd-discuss@lists.sourceforge.net
Subject: Re: [patch] pci/hotplug acpiphp: fix Kconfig for Dock dependencies
Date: Wed, 26 Jul 2006 10:32:26 -0700 [thread overview]
Message-ID: <20060726103226.69aa79c1.kristen.c.accardi@intel.com> (raw)
In-Reply-To: <20060725164125.A15861@unix-os.sc.intel.com>
---
I confirmed that Anil's patch will work, here is a proper patch with
Anil's changes.
Change the build options for acpiphp so that it may build without being
dependent on the ACPI_DOCK option, but yet does not allow the option of
acpiphp being built-in when dock is built as a module.
Signed-off-by: Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>
Signed-off-by: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
---
drivers/pci/hotplug/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- 2.6-git.orig/drivers/pci/hotplug/Kconfig
+++ 2.6-git/drivers/pci/hotplug/Kconfig
@@ -76,7 +76,7 @@ config HOTPLUG_PCI_IBM
config HOTPLUG_PCI_ACPI
tristate "ACPI PCI Hotplug driver"
- depends on ACPI_DOCK && HOTPLUG_PCI
+ depends on (!ACPI_DOCK && ACPI && HOTPLUG_PCI) || (ACPI_DOCK && HOTPLUG_PCI)
help
Say Y here if you have a system that supports PCI Hotplug using
ACPI.
next prev parent reply other threads:[~2006-07-26 17:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 23:18 Kristen Carlson Accardi
2006-07-25 23:41 ` Keshavamurthy Anil S
2006-07-26 0:13 ` Randy.Dunlap
2006-07-26 12:02 ` Keshavamurthy Anil S
2006-07-26 17:32 ` Kristen Carlson Accardi [this message]
2006-07-27 0:23 ` Roman Zippel
2006-08-16 4:59 Brown, Len
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=20060726103226.69aa79c1.kristen.c.accardi@intel.com \
--to=kristen.c.accardi@intel.com \
--cc=akpm@osdl.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=greg@kroah.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pcihpd-discuss@lists.sourceforge.net \
--cc=rdunlap@xenotime.net \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®