From: Greg KH <gregkh@linuxfoundation.org>
To: Bill Pemberton <wfp5p@viridian.itc.virginia.edu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Grant Likely <grant.likely@secretlab.ca>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 000/493] remove CONFIG_HOTPLUG as an option
Date: Wed, 21 Nov 2012 11:15:42 -0800 [thread overview]
Message-ID: <20121121191542.GA23422@kroah.com> (raw)
In-Reply-To: <20121121184146.A9BCB8013C@viridian.itc.virginia.edu>
On Wed, Nov 21, 2012 at 01:41:46PM -0500, Bill Pemberton wrote:
> Andrew Morton writes:
> >
> > On Tue, 20 Nov 2012 10:46:11 +0000 Grant Likely <grant.likely@secretlab.ca> wrote:
> >
> > > On Sat, Nov 17, 2012 at 12:19 AM, Bill Pemberton <wfp5p@virginia.edu> 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.
> > > >
> > > >
> > > > Bill Pemberton (493):
> > > [...]
> > > > 2942 files changed, 11645 insertions(+), 12116 deletions(-)
> > >
> > > So, I've got no problem with the reason for the change and I don't
> > > even think you need my ack for the bits that I maintain (though you
> > > have it if you want it). However, this looks like it is going to be
> > > /painful/. First of all it will touch a huge number of files in the
> > > tree. Yes the change is trivial, but it will require manual fixups on
> > > a lot of patches.
> >
> > Yeah, this is dopey. Send the script to Linus and ask him to run it
> > seven seconds before he releases -rc1, when everyone's trees are
> > empty(ish). Or send him a single megapatch at that time.
> >
>
> I like the script idea for removing all the __dev markings. Creating
> the patches in the first place was a game of whack-a-mole as various
> trees changed.
Linus doesn't like to take scripts, I had planned on queueing all of
these up that different subsystems maintainers didn't take, and pushing
the ones that did merge cleanly into -rc1. Then, right after -rc1 is
out, go through the tree once more to get the stragglers.
Sound reasonable?
thanks,
greg k-h
next prev parent reply other threads:[~2012-11-21 19:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-17 0:19 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
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 [this message]
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=20121121191542.GA23422@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=wfp5p@viridian.itc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome