[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121119202800.GA9083@kroah.com>
Date: Mon, 19 Nov 2012 12:28:00 -0800
From: Greg KH <gregkh@...uxfoundation.org>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Bill Pemberton <wfp5p@...ginia.edu>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 000/493] remove CONFIG_HOTPLUG as an option
On Mon, Nov 19, 2012 at 09:27:09PM +0100, Rafael J. Wysocki wrote:
> On Monday, November 19, 2012 12:01:49 PM Greg KH wrote:
> > On Mon, Nov 19, 2012 at 11:55:56AM -0800, Dmitry Torokhov wrote:
> > > On Fri, Nov 16, 2012 at 07:19:10PM -0500, Bill Pemberton wrote:
> > > > CONFIG_HOTPLUG is no longer an optional setting. In order to remove
> > > > it as on option code paths that check CONFIG_HOTPLUG will removed
> > > > along with the attributes __devexit_p, __devexit, __devinitconst, and
> > > > __devinitdata.
> > > >
> > > > I'll save the list from the mailbomb of this huge patchset. The
> > > > patches themselves are going to Greg KH for the driver core tree.
> > > >
> > >
> > > _iff_ we are going to do this I'd prefer pushing input pieces through my
> > > tree to limit clashes with other work.
> >
> > That's fine with me. I'll ignore any drivers/input/ patches then, is
> > that ok?
>
> Please do the same for PM/ACPI.
Ok, will do.
> Do I need to pull anything for those patches to compile without problems?
Nope, it's just the removal of a symbol, that for 3.7, is defined away
to be an empty string anyway :)
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