From: "Yang, Yi" <yi.y.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Jiri Benc <jbenc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: dev-yBygre7rU0TnMu66kgdUjQ@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH net-next] NSH(Network Service Header) implementation
Date: Mon, 13 Jun 2016 19:35:43 +0800 [thread overview]
Message-ID: <20160613113543.GA39084@cran64.bj.intel.com> (raw)
In-Reply-To: <20160613121114.7c55fd14@griffin>
On Mon, Jun 13, 2016 at 12:11:14PM +0200, Jiri Benc wrote:
> On Sun, 12 Jun 2016 15:53:50 +0800, Yang, Yi wrote:
> > Will use net device after those patches are merged into net-next, It
> > seems current net device implementation in net-next doesn't include it,
>
> The current kernel should have everything that's needed for VXLAN-GPE
> support.
>
> > do you mean this one
> > "http://article.gmane.org/gmane.network.openvswitch.devel/64799"?
>
> This patchset is absolutely needed for ovs to support new VXLAN
> features, including VXLAN-GPE.
>
> Jiri
Got it, I'll rework it after Simon and Thadeu Lima de Souza Cascardo's
patches are merged.
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
prev parent reply other threads:[~2016-06-13 11:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 9:34 [PATCH net-next] NSH(Network Service Header) implementation Yi Yang
[not found] ` <1465205686-96724-1-git-send-email-yi.y.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-06-07 0:45 ` pravin shelar
[not found] ` <CAOrHB_DF+LvRyJAOu6h=ofbf-T-Q85FutsFZ118FhsCsLsVBCg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-06-12 7:53 ` Yang, Yi
2016-06-13 10:11 ` [ovs-dev] " Jiri Benc
2016-06-13 11:35 ` Yang, Yi [this message]
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=20160613113543.GA39084@cran64.bj.intel.com \
--to=yi.y.yang-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=dev-yBygre7rU0TnMu66kgdUjQ@public.gmane.org \
--cc=jbenc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.