From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: The Plan
Date: Tue, 24 Mar 2009 22:03:28 -0400 [thread overview]
Message-ID: <49C990F0.2080207@hp.com> (raw)
In-Reply-To: <20090324.153506.44330862.davem@davemloft.net>
David Miller wrote:
> Everything in net-2.6 right now, as well as the final fix
> we come up with for the GRO issue will get sucked into
> net-next-2.6 as well as queued up for -stable.
>
> Everything in patchwork right now will either be merged
> into net-next-2.6 or tossed.
>
Hi David
Can you give any indication which way you are leaning on the IPv6 binding
patches?
I have some updates and can resubmit if you are planning on taking them.
Thanks
-vlad
next prev parent reply other threads:[~2009-03-25 2:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 22:35 The Plan David Miller
2009-03-24 22:43 ` Ramkrishna Vepa
2009-03-24 22:48 ` David Miller
2009-03-25 2:03 ` Vlad Yasevich [this message]
2009-03-25 2:06 ` 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=49C990F0.2080207@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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).