From: David Miller <davem@davemloft.net>
To: gregkh@linuxfoundation.org
Cc: wfp5p@viridian.itc.virginia.edu, netdev@vger.kernel.org
Subject: Re: respin of __dev* removal patches
Date: Fri, 30 Nov 2012 22:20:21 -0500 (EST) [thread overview]
Message-ID: <20121130.222021.1095074411846638107.davem@davemloft.net> (raw)
In-Reply-To: <20121130233947.GA17353@kroah.com>
From: Greg KH <gregkh@linuxfoundation.org>
Date: Fri, 30 Nov 2012 15:39:47 -0800
> On Fri, Nov 30, 2012 at 05:15:54PM -0500, Bill Pemberton wrote:
>> I've got a respin of the hotplug removal patches for the networking
>> subsystem. I don't want to irritate you like the big patch set did,
>> so before I submit them, what do you want to see that will keep your
>> pain to a minimum?
>>
>> I've redone them so that all the __dev* removals are done at once so
>> there won't be one patch for __devinit, one for __devexit, etc. I've
>> also broken them down into chunks following what's in the MAINTAINERS
>> file. The result is 103 patches.
>
> As that's a lot of patches to handle through patchwork, would it be
> easier for the network maintainers for me to just put these in a tree
> they can pull from? I will base it off of net-next.
That might work.
prev parent reply other threads:[~2012-12-01 3:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 22:15 respin of __dev* removal patches Bill Pemberton
2012-11-30 23:39 ` Greg KH
2012-12-01 3:20 ` David Miller [this message]
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=20121130.222021.1095074411846638107.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).