From: Jeff Garzik <jeff@garzik•org>
To: netdev@vger•kernel.org
Cc: David Miller <davem@davemloft•net>
Subject: Re: net-next-2.6...
Date: Mon, 27 Oct 2008 14:53:56 -0400 [thread overview]
Message-ID: <49060E44.5070604@garzik.org> (raw)
In-Reply-To: <20081027.113503.149366323.davem@davemloft.net>
David Miller wrote:
> Stephen Rothwell said earlier today that it's OK to "let it rip"
> and allow new changes to start flowing into the linux-next tree.
>
> So I'll likely get the net-next-2.6 going today.
>
> First I'll cut the tree with a fresh clone of Linus's current stuff,
> then add in all the things which are in the queue already (Neil's
> routing cache hacks, Thomas Graf's cgroup work, the print_mac() %pX
> bits, etc.)
>
> As always you can get a good idea of what will be looked at and considered
> by taking a look at the patchwork queue for netdev:
>
> http://patchwork.ozlabs.org/
>
> I'll make another posting when the new tree is up and operational.
Likewise, as soon as net-next-2.6 opens, I'll be taking patches for
drivers/net/*
Jeff
next prev parent reply other threads:[~2008-10-27 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 18:35 net-next-2.6 David Miller
2008-10-27 18:53 ` Jeff Garzik [this message]
2008-10-28 1:56 ` net-next-2.6 David Miller
-- strict thread matches above, loose matches on Subject: below --
2010-03-15 23:18 net-next-2.6 David Miller
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=49060E44.5070604@garzik.org \
--to=jeff@garzik$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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