Commit 45f035ab authored by Greg Kroah-Hartman's avatar Greg Kroah-Hartman
Browse files

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: default avatarGreg Kroah-Hartman <>
Cc: Geert Uytterhoeven <>
Cc: Ralf Baechle <>
Cc: Bjorn Helgaas <>
parent 1a91b016
......@@ -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
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
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment