From: Adrian Bunk <bunk@stusta.de>
To: "Brown, Len" <len.brown@intel.com>
Cc: Miles Lane <miles.lane@gmail.com>,
"Accardi, Kristen C" <kristen.c.accardi@intel.com>,
Dave Hansen <haveblue@us.ibm.com>, Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
gregkh@suse.de, linux-acpi@vger.kernel.org,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: 2.6.17-mm2 -- drivers/built-in.o: In function `is_pci_dock_device':acpiphp_glue.c:(.text+0x12364): undefined reference to `is_dock_device'
Date: Mon, 10 Jul 2006 01:12:18 +0200 [thread overview]
Message-ID: <20060709231218.GU13938@stusta.de> (raw)
In-Reply-To: <CFF307C98FEABE47A452B27C06B85BB6ECF9E7@hdsmsx411.amr.corp.intel.com>
On Sun, Jul 09, 2006 at 07:03:23PM -0400, Brown, Len wrote:
>
> >It would be a solution to let HOTPLUG_PCI_ACPI depend on
> >(ACPI_DOCK || ACPI_DOCK=n), or the #if in
> >include/acpi/acpi_drivers.h could be changed to
> >#if defined(CONFIG_ACPI_DOCK) ||
> >(defined(CONFIG_ACPI_DOCK_MODULE) && defined(MODULE))
>
> CONFIG_HOTPLUG_PCI_ACPI requires CONFIG_ACPI_DOCK.
> There are 9 combinations.
>
> DOCK HPA
> n n ok
> n y illegal
> n m illegal
> y n ok
> y y ok
> y m ok
> m n ok
> m y illegal (subject of this thread)
> m m ok
>
> The patch below handles all these cases:
>
> DOCK HPA
> n n builds
> n y -> y,y
> n m -> m,m
> y n builds
> y y builds
> y m builds
> m n builds
> m y -> m,y
> m m builds
>
> okay?
This patch looks wrong since it allows the illegal configuration
ACPI_IBM_DOCK=y, HOTPLUG_PCI_ACPI=y/m, ACPI_DOCK=y/m.
If you select something, you have to ensure the dependencies of what you
are select'ing are fulfilled.
config HOTPLUG_PCI_ACPI
tristate "ACPI PCI Hotplug driver"
depends on ACPI && HOTPLUG_PCI
depends on !ACPI_IBM_DOCK
select ACPI_DOCK
help
...
> -Len
>
> diff --git a/drivers/pci/hotplug/Kconfig b/drivers/pci/hotplug/Kconfig
> index 222a1cc..e7c955b 100644
> --- a/drivers/pci/hotplug/Kconfig
> +++ b/drivers/pci/hotplug/Kconfig
> @@ -78,6 +78,7 @@ config HOTPLUG_PCI_IBM
> config HOTPLUG_PCI_ACPI
> tristate "ACPI PCI Hotplug driver"
> depends on ACPI && HOTPLUG_PCI
> + select ACPI_DOCK
> help
> Say Y here if you have a system that supports PCI Hotplug
> using
> ACPI.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-07-09 23:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 23:03 2.6.17-mm2 -- drivers/built-in.o: In function `is_pci_dock_device':acpiphp_glue.c:(.text+0x12364): undefined reference to `is_dock_device' Brown, Len
2006-07-09 23:03 ` Brown, Len
2006-07-09 23:12 ` Adrian Bunk [this message]
2006-07-10 1:46 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2006-07-10 2:02 Brown, Len
2006-07-10 2:02 ` Brown, Len
2006-07-09 23:06 Brown, Len
2006-07-09 23:06 ` Brown, Len
2006-06-25 19:56 Miles Lane
2006-06-25 20:09 ` Adrian Bunk
2006-06-25 20:13 ` Miles Lane
2006-06-25 20:40 ` Adrian Bunk
2006-06-26 5:56 ` Keith Owens
2006-06-26 6:22 ` Keith Owens
2006-06-26 22:15 ` Roman Zippel
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=20060709231218.GU13938@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=haveblue@us.ibm.com \
--cc=kristen.c.accardi@intel.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
--cc=torvalds@osdl.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.