From: Adrian Bunk <bunk@stusta.de>
To: Miles Lane <miles.lane@gmail.com>,
Kristen Accardi <kristen.c.accardi@intel.com>,
Dave Hansen <haveblue@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
gregkh@suse.de, len.brown@intel.com, linux-acpi@vger.kernel.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: Sun, 25 Jun 2006 22:09:53 +0200 [thread overview]
Message-ID: <20060625200953.GF23314@stusta.de> (raw)
In-Reply-To: <a44ae5cd0606251256m74182e7fw4eb2692c89b0e2f8@mail.gmail.com>
On Sun, Jun 25, 2006 at 12:56:44PM -0700, Miles Lane wrote:
> drivers/built-in.o: In function
> `is_pci_dock_device':acpiphp_glue.c:(.text+0x12364): undefined
> reference to `is_dock_device'
> drivers/built-in.o: In function
> `cleanup_bridge':acpiphp_glue.c:(.text+0x12bc4): undefined reference
> to `is_dock_device'
> :acpiphp_glue.c:(.text+0x12bd3): undefined reference to
> `unregister_hotplug_dock_device'
> :acpiphp_glue.c:(.text+0x12bdb): undefined reference to
> `unregister_dock_notifier'
> drivers/built-in.o: In function
> `register_slot':acpiphp_glue.c:(.text+0x13ac0): undefined reference to
> `is_dock_device'
> :acpiphp_glue.c:(.text+0x13cd9): undefined reference to `is_dock_device'
> :acpiphp_glue.c:(.text+0x13cf0): undefined reference to
> `register_hotplug_dock_device'
> :acpiphp_glue.c:(.text+0x13d1d): undefined reference to
> `register_dock_notifier'
> make: *** [.tmp_vmlinux1] Error 1
>
> #
> # PCI Hotplug Support
> #
> CONFIG_HOTPLUG_PCI=y
> CONFIG_HOTPLUG_PCI_FAKE=y
> CONFIG_HOTPLUG_PCI_COMPAQ=y
> # CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM is not set
> CONFIG_HOTPLUG_PCI_ACPI=y
> CONFIG_HOTPLUG_PCI_ACPI_IBM=y
> CONFIG_HOTPLUG_PCI_CPCI=y
> # CONFIG_HOTPLUG_PCI_CPCI_ZT5550 is not set
> CONFIG_HOTPLUG_PCI_CPCI_GENERIC=y
> CONFIG_HOTPLUG_PCI_SHPC=y
> # CONFIG_HOTPLUG_PCI_SHPC_POLL_EVENT_MODE is not set
You hadn't attached your complete .config, but is it correct when I
assume you have CONFIG_ACPI_DOCK=m? This would explain the problem.
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-06-25 20:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-25 19:56 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' Miles Lane
2006-06-25 20:09 ` Adrian Bunk [this message]
2006-06-25 20:13 ` Miles Lane
2006-06-25 20:40 ` Adrian Bunk
2006-07-09 0:06 ` ACPI_DOCK bug: noone cares Adrian Bunk
2006-07-09 16:01 ` Linus Torvalds
2006-06-26 5:56 ` 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' Keith Owens
2006-06-26 6:22 ` Keith Owens
2006-06-26 22:15 ` Roman Zippel
-- strict thread matches above, loose matches on Subject: below --
2006-07-09 23:03 Brown, Len
2006-07-09 23:12 ` Adrian Bunk
2006-07-10 1:46 ` Linus Torvalds
2006-07-09 23:06 Brown, Len
2006-07-10 2:02 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=20060625200953.GF23314@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 \
/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