[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120906202815.GA6732@kroah.com>
Date: Thu, 6 Sep 2012 13:28:16 -0700
From: Greg KH <gregkh@...uxfoundation.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>,
Ralf Baechle <ralf@...ux-mips.org>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Chris Metcalf <cmetcalf@...era.com>,
Chris Zankel <chris@...kel.net>
Cc: linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [patch 0/3] Turn CONFIG_HOTPLUG always on.
On Tue, Sep 04, 2012 at 05:01:05PM -0700, Greg Kroah-Hartman wrote:
> From: Greg KH <gregkh@...uxfoundation.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.
Given the lack of objection, I've now queued these up for 3.7 and will
start unwinding the CONFIG_HOTPLUG mess.
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists