From: Cong Wang <amwang@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Jesse Gross <jesse@nicira.com>,
Pravin B Shelar <pshelar@nicira.com>
Subject: Re: Where are OVS VXLAN patches?
Date: Fri, 16 Aug 2013 12:50:25 +0800 [thread overview]
Message-ID: <1376628625.2934.57.camel@cr0> (raw)
In-Reply-To: <CAOaVG16Vx11DV4gxfSf2f0BceOk1y+aP6rtz-_h9b0Ckp0r2Jw@mail.gmail.com>
(Re-adding netdev and davem...)
On Thu, 2013-08-15 at 21:33 -0700, Stephen Hemminger wrote:
> Send them to netdev. The vxlan-next tree was temporary when there were
> 3 people working on VXLAN at
> same time (Pravin, ong, and me). I see no point in keeping a separate
> tree over the long term.
>
I agree. There is some misunderstanding between you and David on taking
these patches. :)
next prev parent reply other threads:[~2013-08-16 4:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 7:07 Where are OVS VXLAN patches? Cong Wang
2013-08-12 7:52 ` David Miller
2013-08-12 16:59 ` Jesse Gross
2013-08-13 5:16 ` Cong Wang
[not found] ` <1376615540.2934.3.camel@cr0>
[not found] ` <CAOaVG16Vx11DV4gxfSf2f0BceOk1y+aP6rtz-_h9b0Ckp0r2Jw@mail.gmail.com>
2013-08-16 4:50 ` Cong Wang [this message]
2013-08-16 15:58 ` Jesse Gross
2013-08-19 1:23 ` Cong Wang
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=1376628625.2934.57.camel@cr0 \
--to=amwang@redhat.com \
--cc=davem@davemloft.net \
--cc=jesse@nicira.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.com \
--cc=stephen@networkplumber.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).