Since FW_LOADER is an option that is always select'ed by the code using
it, it mustn't depend on HOTPLUG.
It's only relevant in the EMBEDDED=y case, but this might have resulted
in illegal FW_LOADER=, HOTPLUG=n configurations.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
--- linux-2.6.19-rc6-mm2/drivers/base/Kconfig.old 2006-12-02
20:36:49.000000000 +0100
+++ linux-2.6.19-rc6-mm2/drivers/base/Kconfig 2006-12-02 20:37:03.000000000
+0100
@@ -19,8 +19,8 @@
If unsure say Y here.
config FW_LOADER
- tristate "Userspace firmware loading support"
- depends on HOTPLUG
+ tristate
+ select HOTPLUG
---help---
This option is provided for the case where no in-kernel-tree modules
require userspace firmware loading support, but a module built outside
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
