From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Ralf Baechle <ralf@linux-mips.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Chris Metcalf <cmetcalf@tilera.com>,
Chris Zankel <chris@zankel.net>
Subject: [patch 3/3] CONFIG_HOTPLUG should be always on
Date: Tue, 4 Sep 2012 17:01:08 -0700 [thread overview]
Message-ID: <20120904235155.218456468@clark.kroah.org> (raw)
In-Reply-To: <20120904234803.554552301@clark.kroah.org>
[-- Attachment #1: config_hotplug-should-be-always-on.patch --]
[-- Type: text/plain, Size: 1525 bytes --]
From: Greg KH <gregkh@linuxfoundation.org>
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 <gregkh@linuxfoundation.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>
---
init/Kconfig | 8 +-------
1 file changed, 1 insertion(+), 7 deletions(-)
--- 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
next prev parent reply other threads:[~2012-09-05 0:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 0:01 [patch 0/3] Turn CONFIG_HOTPLUG always on Greg Kroah-Hartman
2012-09-05 0:01 ` [patch 1/3] xtensa: remove duplicate CONFIG_HOTPLUG definition Greg Kroah-Hartman
2012-09-05 0:01 ` [patch 2/3] tile: " Greg Kroah-Hartman
2012-09-05 0:56 ` Chris Metcalf
2012-09-05 0:01 ` Greg Kroah-Hartman [this message]
2012-09-06 20:28 ` [patch 0/3] Turn CONFIG_HOTPLUG always on Greg KH
2012-10-05 8:50 ` Andrew Morton
2012-10-05 14:32 ` Greg KH
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=20120904235155.218456468@clark.kroah.org \
--to=gregkh@linuxfoundation.org \
--cc=bhelgaas@google.com \
--cc=chris@zankel.net \
--cc=cmetcalf@tilera.com \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.org \
/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;
as well as URLs for NNTP newsgroup(s).