From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: 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>
Cc: Greg KH <gregkh@linuxfoundation.org>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [patch 0/3] Turn CONFIG_HOTPLUG always on.
Date: Tue, 4 Sep 2012 17:01:05 -0700 [thread overview]
Message-ID: <20120904234803.554552301@clark.kroah.org> (raw)
From: Greg KH <gregkh@linuxfoundation.org>
The CONFIG_HOTPLUG variable is tough to turn off, and almost all arches
default to it on.
If you turn it off, it saves you a big 200 or so bytes, and then starts
to cause all sorts of problems as the code paths if the option is
disabled is never really tested, and memory segments start to get thrown
away that driver authors assume will always be present.
So, as part of trying to get rid of the option entirely, let's just turn
the option always on.
Note, to do this properly, I found two duplicate definitions of the
option, in the Tile and Xtensa arch files, this patch series removes
those duplicates first.
Anyone object to me just taking these three patches through my
driver-core tree for 3.7? After this set, I'll start unwinding the
places where CONFIG_HOTPLUG is used and remove the parts that are not
used anymore now that the option can not be turned off.
thanks,
greg k-h
next reply other threads:[~2012-09-05 0:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 0:01 Greg Kroah-Hartman [this message]
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 ` [patch 3/3] CONFIG_HOTPLUG should be always on Greg Kroah-Hartman
2012-09-06 20:28 ` [patch 0/3] Turn CONFIG_HOTPLUG " 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=20120904234803.554552301@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).