From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Joe Perches <joe@perches.com>
Cc: netdev <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Jan Engelhardt <jengelh@medozas.de>
Subject: Re: [RFC] Moving files around in drivers/net
Date: Wed, 15 Jun 2011 11:38:43 -0700 [thread overview]
Message-ID: <BANLkTi=BAqKzZeLF2_uCYnr7PD3StGFgAg@mail.gmail.com> (raw)
In-Reply-To: <1306958478.32125.32.camel@Joe-Laptop>
On Wed, Jun 1, 2011 at 13:01, Joe Perches <joe@perches.com> wrote:
> On Wed, 2011-06-01 at 12:53 -0700, Jeff Kirsher wrote:
>> On Wed, 2011-06-01 at 12:30 -0700, Joe Perches wrote:
>> > Does anyone still think moving files around in drivers/net
>> > would be sensible and a suitable candidate for inclusion
>> > in 3.1?
>> > Here's what Jeffrey proposed:
>> > http://vger.kernel.org/netconf2010_slides/netconf-jtk.pdf
>> > Here's what I proposed before that.
>> > http://www.spinics.net/lists/netdev/msg149717.html
>> I am over 90% done with the work and have been trying to finish up the
>> patches so that I could get them out as an RFC here in the next week.
>
> Excellent, thanks.
>
I thought for sure I would have finished what I have left by last
weekend, but I keep getting interrupted. (Blame it on the NHL stanley
cup playoffs) :)
I have created a git tree on kernel.org with all the work that I have
completed so far (see below). This first stage of the move is only
taking care of the drivers. The next stage will move the networking
core drivers (bridging, bonding, vlan, etc.) into drivers/net/sw.
git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-organize
I will send out all the patches as an RFC by the end of the week (for sure).
--
Cheers,
Jeff
next prev parent reply other threads:[~2011-06-15 18:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 19:30 [RFC] Moving files around in drivers/net Joe Perches
2011-06-01 19:53 ` Jeff Kirsher
2011-06-01 20:01 ` Joe Perches
2011-06-15 18:38 ` Jeff Kirsher [this message]
2011-06-15 20:35 ` Andy Gospodarek
2011-06-16 1:10 ` Joe Perches
2011-06-16 3:34 ` Po-Yu Chuang
2011-06-20 1:42 ` Jeff Kirsher
2011-06-16 5:05 ` Sathya.Perla
2011-06-20 1:48 ` Jeff Kirsher
2011-06-16 14:14 ` Jon Mason
2011-06-20 1:51 ` Jeff Kirsher
2011-06-16 15:03 ` Jon Mason
2011-06-20 1:59 ` Jeff Kirsher
2011-06-20 15:23 ` Jon Mason
2011-06-23 13:30 ` Giuseppe CAVALLARO
2011-06-24 3:56 ` Jeff Kirsher
2011-06-20 2:25 ` Jeff Kirsher
2011-06-20 3:22 ` Ben Hutchings
2011-06-20 4:02 ` Jeff Kirsher
2011-06-20 5:23 ` Jan Engelhardt
2011-06-20 6:01 ` Joe Perches
2011-06-01 21:07 ` Ben Hutchings
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='BANLkTi=BAqKzZeLF2_uCYnr7PD3StGFgAg@mail.gmail.com' \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=jengelh@medozas.de \
--cc=joe@perches.com \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
/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).