From 45f035ab9b8f45aaf1eb2213218b7e9c14af3fc2 Mon Sep 17 00:00:00 2001 From: Greg Kroah-Hartman Date: Tue, 4 Sep 2012 17:01:08 -0700 Subject: CONFIG_HOTPLUG should be always on CONFIG_HOTPLUG is a very old option, back when we had static systems and it was odd that any type of device would be removed or added after the system had started up. It is quite hard to disable it these days, and even if you do, it only saves you about 200 bytes. However, if it is disabled, lots of bugs show up because it is almost never tested if the option is disabled. This is a step to eventually just remove the option entirely, which will clean up all of the devinit* variable and function pointer options, that everyone (myself include) ends up getting wrong eventually, causing real problems when memory segments are removed yet we don't expect them to be. Signed-off-by: Greg Kroah-Hartman Cc: Geert Uytterhoeven Cc: Ralf Baechle Cc: Bjorn Helgaas --- init/Kconfig | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) (limited to 'init') diff --git a/init/Kconfig b/init/Kconfig index af6c7f8..af67c43 100644 --- a/init/Kconfig +++ b/init/Kconfig @@ -1201,13 +1201,7 @@ config KALLSYMS_ALL Say N unless you really need all symbols. config HOTPLUG - bool "Support for hot-pluggable devices" if EXPERT - default y - help - This option is provided for the case where no hotplug or uevent - capabilities is wanted by the kernel. You should only consider - disabling this option for embedded systems that do not use modules, a - dynamic /dev tree, or dynamic device discovery. Just say Y. + def_bool y config PRINTK default y -- cgit v1.1