All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Bill Pemberton <wfp5p@virginia.edu>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 000/493] remove CONFIG_HOTPLUG as an option
Date: Mon, 19 Nov 2012 12:28:00 -0800	[thread overview]
Message-ID: <20121119202800.GA9083@kroah.com> (raw)
In-Reply-To: <2170877.01mKLSMGf6@vostro.rjw.lan>

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

  reply	other threads:[~2012-11-19 20:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-17  0:19 [PATCH 000/493] remove CONFIG_HOTPLUG as an option Bill Pemberton
2012-11-19 19:55 ` Dmitry Torokhov
2012-11-19 20:01   ` Greg KH
2012-11-19 20:27     ` Rafael J. Wysocki
2012-11-19 20:28       ` Greg KH [this message]
2012-11-24  8:26   ` Dmitry Torokhov
2012-11-20  3:11 ` viresh kumar
2012-11-20 10:46 ` Grant Likely
2012-11-21  7:56   ` Andrew Morton
2012-11-21 18:41     ` Bill Pemberton
2012-11-21 19:15       ` Greg KH
2012-11-21 23:55         ` Grant Likely
2012-11-22  1:07           ` Bill Pemberton
2012-12-06  0:27             ` Grant Likely
2012-12-06  0:39               ` Greg KH
2012-12-07 13:47                 ` Grant Likely
2012-12-07 17:16                   ` Greg KH
2012-12-07 23:04                     ` Grant Likely
2012-11-21 23:05     ` Grant Likely

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=20121119202800.GA9083@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=wfp5p@virginia.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.