From: David Miller <davem@davemloft.net>
To: pshelar@nicira.com
Cc: netdev@vger.kernel.org, stephen@networkplumber.org
Subject: Re: [PATCH net-next v7 0/8] openvswitch: VXLAN tunneling.
Date: Tue, 20 Aug 2013 00:17:12 -0700 (PDT) [thread overview]
Message-ID: <20130820.001712.1951982778222810447.davem@davemloft.net> (raw)
In-Reply-To: <1376936559-25427-1-git-send-email-pshelar@nicira.com>
From: Pravin B Shelar <pshelar@nicira.com>
Date: Mon, 19 Aug 2013 11:22:39 -0700
> First four vxlan patches extends vxlan so that openvswitch
> can share vxlan recv code. Rest of patches refactors vxlan
> data plane so that ovs can share that code with vxlan module.
> Last patch adds vxlan-vport to openvswitch.
>
> v7 fixed first patch as suggested by Stephen Hemminger.
> v6 series splits second patch into two and has few style fixes.
> v5 series disallow any udp port sharing between
> kernel-vxlan and ovs-vxlan as suggested by Stephen Hemminger.
Series applied, thanks.
next prev parent reply other threads:[~2013-08-20 7:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 18:22 [PATCH net-next v7 0/8] openvswitch: VXLAN tunneling Pravin B Shelar
2013-08-20 7:17 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-05 17:47 Pravin B Shelar
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=20130820.001712.1951982778222810447.davem@davemloft.net \
--to=davem@davemloft.net \
--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).