linux-kernel - Re: In function `ata_acpi_associate': undefined reference to `register_hotplug_dock

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200803172357.54253.lenb@kernel.org>
Date:	Mon, 17 Mar 2008 23:57:53 -0400
From:	Len Brown <lenb@...nel.org>
To:	Thomas Meyer <thomas@...3r.de>,
	Kristen Carlson Accardi <kristen.c.accardi@...el.com>,
	linux-acpi@...r.kernel.org
Cc:	Adrian Bunk <bunk@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	htejun@...il.com, jeff@...zik.org
Subject: Re: In function `ata_acpi_associate': undefined reference to	`register_hotplug_dock_device'

> drivers/built-in.o: In function `ata_acpi_associate':
> (.text+0x7106a): undefined reference to `register_hotplug_dock_device'

CONFIG_ACPI_DOCK=m
CONFIG_ATA_ACPI=y

don't work together.

particularly this:

drivers/ata/libata-acpi.c
...
#if defined(CONFIG_ACPI_DOCK) || defined(CONFIG_ACPI_DOCK_MODULE)
                        /* we might be on a docking station */
                        register_hotplug_dock_device(ap->acpi_handle,
                                                     ata_acpi_ap_notify, ap);
#endif

does not link with an EXPORT_SYMBOL_GPL in dock.c when that is a module.

you can change them both to be =y (or either to be =n) to work around it.
however, this is a 2.6.25 regression, since 2.6.24 could make ATA=y
and make dock=m

-Len
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/