public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Thomas Meyer <thomas@m3y3r.de>,
	Kristen Carlson Accardi <kristen.c.accardi@intel.com>,
	linux-acpi@vger.kernel.org
Cc: Adrian Bunk <bunk@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	htejun@gmail.com, jeff@garzik.org
Subject: Re: In function `ata_acpi_associate': undefined reference to	`register_hotplug_dock_device'
Date: Mon, 17 Mar 2008 23:57:53 -0400	[thread overview]
Message-ID: <200803172357.54253.lenb@kernel.org> (raw)
In-Reply-To: <47DECD54.5060202@m3y3r.de>

> 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

  reply	other threads:[~2008-03-18  3:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-17 19:41 In function `ata_acpi_associate': undefined reference to `register_hotplug_dock_device' Thomas Meyer
2008-03-17 19:48 ` Adrian Bunk
2008-03-17 19:58   ` Thomas Meyer
2008-03-18  3:57     ` Len Brown [this message]
2008-03-18  4:11       ` [PATCH] " Len Brown
2008-03-18  6:16         ` Tejun Heo
2008-03-17 20:30 ` [2.6.25 patch] acpi_drivers.h: fix dock dummy functions 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=200803172357.54253.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=bunk@kernel.org \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=kristen.c.accardi@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas@m3y3r.de \
    /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