[QUESTION] 2.4.3: hotplug_path unresolved in usbcore?

From: Ryan Mack (rmack@mackman.net)
Date: Thu Apr 05 2001 - 01:46:14 EST

Next message: CaT: "2.4.3-ac2 and D state process"
Previous message: Dawson Engler: "[CHECKER] __init functions called by non-__init"
In reply to: Eric Gillespie: "Re: More about 2.4.3 timer problems"
Next in thread: Bart Trojanowski: "Re: [QUESTION] 2.4.3: hotplug_path unresolved in usbcore?"
Reply: Bart Trojanowski: "Re: [QUESTION] 2.4.3: hotplug_path unresolved in usbcore?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Sorry for such a stupid question, but I'm stumped (it doesn't take much).
modprobe reports that hotplug_path is unresolved when it processes
usbcore. CONFIG_HOTPLUG is defined, so it seems that hotplug_path is
defined and EXPORTed in kernel/kmod.c, so I'm unsure what the problem is.

Thanks, Ryan

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

Next message: CaT: "2.4.3-ac2 and D state process"
Previous message: Dawson Engler: "[CHECKER] __init functions called by non-__init"
In reply to: Eric Gillespie: "Re: More about 2.4.3 timer problems"
Next in thread: Bart Trojanowski: "Re: [QUESTION] 2.4.3: hotplug_path unresolved in usbcore?"
Reply: Bart Trojanowski: "Re: [QUESTION] 2.4.3: hotplug_path unresolved in usbcore?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Apr 07 2001 - 21:00:16 EST