From: Greg KH <greg@kroah.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>, Kay Sievers <kay.sievers@vrfy.org>,
rml@novell.com, linux-kernel@vger.kernel.org,
len.brown@intel.com, acpi-devel@lists.sourceforge.net
Subject: Re: 2.6.10-rc1-mm3: ACPI problem due to un-exported hotplug_path
Date: Fri, 5 Nov 2004 10:05:13 -0800 [thread overview]
Message-ID: <20041105180513.GA32007@kroah.com> (raw)
In-Reply-To: <20041105164523.GC1295@stusta.de>
On Fri, Nov 05, 2004 at 05:45:23PM +0100, Adrian Bunk wrote:
> The following error (compin from Linus' tree) is caused by the fact that
> hotplug_path is no longer EXPORT_SYMBOL'ed:
>
>
> <-- snip -->
>
> if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.6.10-rc1-mm3; fi
> WARNING: /lib/modules/2.6.10-rc1-mm3/kernel/drivers/acpi/container.ko needs unknown symbol hotplug_path
>
> <-- snip -->
Hm, must be an -mm specific change that is causing this. I don't see
this in the current tree.
Len, why would any ACPI code be wanting to get access to hotplug_path
directly?
thanks,
greg k-h
next prev parent reply other threads:[~2004-11-05 18:06 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-05 8:13 2.6.10-rc1-mm3 Andrew Morton
2004-11-05 9:41 ` 2.6.10-rc1-mm3 Lorenzo Allegrucci
2004-11-05 10:17 ` 2.6.10-rc1-mm3 Andrew Morton
2004-11-05 10:48 ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 12:36 ` 2.6.10-rc1-mm3 Lorenzo Allegrucci
2004-11-05 10:22 ` 2.6.10-rc1-mm3 Ingo Molnar
2004-11-05 10:38 ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 11:09 ` 2.6.10-rc1-mm3 Ingo Molnar
2004-11-05 11:17 ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 11:24 ` 2.6.10-rc1-mm3 Ingo Molnar
2004-11-05 11:43 ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 12:15 ` 2.6.10-rc1-mm3 Ingo Molnar
2004-11-05 12:22 ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 12:57 ` 2.6.10-rc1-mm3 Rafael J. Wysocki
2004-11-05 13:02 ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 17:47 ` 2.6.10-rc1-mm3 Rafael J. Wysocki
2004-11-05 11:20 ` 2.6.10-rc1-mm3 Russell King
2004-11-05 11:30 ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 10:17 ` 2.6.10-rc1-mm3 Ingo Molnar
2004-11-05 15:54 ` 2.6.10-rc1-mm3 Michael Baehr
2004-11-05 10:56 ` 2.6.10-rc1-mm3 Con Kolivas
2004-11-05 16:45 ` 2.6.10-rc1-mm3: ACPI problem due to un-exported hotplug_path Adrian Bunk
2004-11-05 18:05 ` Greg KH [this message]
2004-11-05 20:10 ` Kay Sievers
2004-11-05 20:32 ` Ashok Raj
2004-11-05 20:43 ` Greg KH
2004-11-05 20:45 ` Kay Sievers
2004-11-05 20:42 ` Greg KH
2004-11-06 5:18 ` Keshavamurthy Anil S
2004-11-06 5:50 ` Dmitry Torokhov
2004-11-09 22:55 ` Greg KH
2004-11-09 23:48 ` [ACPI] " Dmitry Torokhov
2004-11-10 0:08 ` Greg KH
2004-11-10 4:15 ` Dmitry Torokhov
2004-11-16 5:54 ` Greg KH
2004-11-05 16:52 ` 2.6.10-rc1-mm3: drm_ati_pcigart_{init,cleanup} multiple definition Adrian Bunk
2004-11-05 17:19 ` Dave Airlie
2004-11-05 17:33 ` Jon Smirl
2004-11-05 18:07 ` 2.6.10-rc1-mm3 Rafael J. Wysocki
2004-11-05 18:48 ` 2.6.10-rc1-mm3: (fix for make xconfig) Rafael J. Wysocki
2004-11-05 20:26 ` Sam Ravnborg
2004-11-08 22:34 ` Sam Ravnborg
2004-11-05 18:07 ` 2.6.10-rc1-mm3 Adam Heath
2004-11-06 7:16 ` 2.6.10-rc1-mm3 Pasi Savolainen
2004-11-06 9:39 ` [PATCH][TRIVIAL] sched.c whitespace mangler Con Kolivas
2004-11-07 1:32 ` 2.6.10-rc1-mm3: "bttv card=" breakage Adrian Bunk
2004-11-07 2:15 ` Andrew Morton
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=20041105180513.GA32007@kroah.com \
--to=greg@kroah.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=kay.sievers@vrfy.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@novell.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