Re: [patch 0/3] Turn CONFIG_HOTPLUG always on.

2012-10-05 Thread Greg KH
On Fri, Oct 05, 2012 at 01:50:36AM -0700, Andrew Morton wrote: > On Thu, 6 Sep 2012 13:28:16 -0700 Greg KH wrote: > > > 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 > >

Re: [patch 0/3] Turn CONFIG_HOTPLUG always on.

2012-10-05 Thread Andrew Morton
On Thu, 6 Sep 2012 13:28:16 -0700 Greg KH wrote: > 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 s

Re: [patch 0/3] Turn CONFIG_HOTPLUG always on.

2012-09-06 Thread Greg KH
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

[patch 0/3] Turn CONFIG_HOTPLUG always on.

2012-09-04 Thread Greg Kroah-Hartman
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 s