netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cong Wang <amwang@redhat.com>
To: Jesse Gross <jesse@nicira.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	netdev <netdev@vger.kernel.org>,
	Pravin B Shelar <pshelar@nicira.com>,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: Where are OVS VXLAN patches?
Date: Tue, 13 Aug 2013 13:16:28 +0800	[thread overview]
Message-ID: <1376370988.13583.6.camel@cr0> (raw)
In-Reply-To: <CAEP_g=-JQUZaLUhkMWQ6p8iYn8jqb_0tZOq=x+kv0Xip3dUA7A@mail.gmail.com>

On Mon, 2013-08-12 at 09:59 -0700, Jesse Gross wrote:
> On Mon, Aug 12, 2013 at 12:07 AM, Cong Wang <amwang@redhat.com> wrote:
> > Hello, David
> >
> > I am wondering where are the patches for OVS VXLAN support from Pravin?
> > v7 were posted one week ago:
> > http://marc.info/?l=linux-netdev&m=137572485116601&w=2
> >
> > and no one complains about them, so I think they are ready for merge?
> >
> > But they still do not appear in net-next, nor I can find them in vxlan
> > tree of Stephen or openvswitch tree of Jesse. What's more, I even can't
> > find them in netdev patchwork [1].
> 
> I believe that Stephen is planning on taking the first part of the
> series through his VXLAN tree.

I can't find them here:
https://git.kernel.org/cgit/linux/kernel/git/shemminger/vxlan-next.git

Maybe Stephen hasn't pushed them.

Thanks.

  reply	other threads:[~2013-08-13  5:16 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 [this message]
     [not found]     ` <1376615540.2934.3.camel@cr0>
     [not found]       ` <CAOaVG16Vx11DV4gxfSf2f0BceOk1y+aP6rtz-_h9b0Ckp0r2Jw@mail.gmail.com>
2013-08-16  4:50         ` Cong Wang
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=1376370988.13583.6.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).