archive mirror
 help / color / mirror / Atom feed
From: Greg KH <>
To: Geert Uytterhoeven <>,
	Ralf Baechle <>,
	Bjorn Helgaas <>,
	Chris Metcalf <>,
	Chris Zankel <>
Subject: Re: [patch 0/3] Turn CONFIG_HOTPLUG always on.
Date: Thu, 6 Sep 2012 13:28:16 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, Sep 04, 2012 at 05:01:05PM -0700, Greg Kroah-Hartman wrote:
> From: Greg KH <>
> 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.

Given the lack of objection, I've now queued these up for 3.7 and will
start unwinding the CONFIG_HOTPLUG mess.


greg k-h

  parent reply	other threads:[~2012-09-06 20:30 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 ` [patch 3/3] CONFIG_HOTPLUG should be always on Greg Kroah-Hartman
2012-09-06 20:28 ` Greg KH [this message]
2012-10-05  8:50   ` [patch 0/3] Turn CONFIG_HOTPLUG " 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \

* 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).