public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Jiri Benc <jbenc@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 0/4] vxlan: add VXLAN-GPE support
Date: Mon, 11 Apr 2016 15:17:54 -0700	[thread overview]
Message-ID: <20160411151754.6613c2f1@xeon-e3> (raw)
In-Reply-To: <cover.1460032274.git.jbenc@redhat.com>

On Thu,  7 Apr 2016 14:36:25 +0200
Jiri Benc <jbenc@redhat.com> wrote:

> This patchset adds a couple of refinements to the 'external' keyword and
> adds support for configuring VXLAN-GPE interfaces.
> 
> The VXLAN-GPE support was recently merged to net-next.
> 
> The first patch is not intended to be applied directly but I still include
> it in order for this patchset to be compilable and testable by those
> interested.
> 
> Jiri Benc (4):
>   if_link.h: rebase to the kernel
>   vxlan: 'external' implies 'nolearning'
>   ip-link.8: document "external" flag for vxlan
>   vxlan: add support for VXLAN-GPE
> 
>  include/linux/if_link.h |  1 +
>  ip/iplink_vxlan.c       | 14 ++++++++++++--
>  man/man8/ip-link.8.in   | 17 +++++++++++++++++
>  3 files changed, 30 insertions(+), 2 deletions(-)
> 

Applied to net-next

      parent reply	other threads:[~2016-04-11 22:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07 12:36 [PATCH iproute2 0/4] vxlan: add VXLAN-GPE support Jiri Benc
2016-04-07 12:36 ` [PATCH iproute2 1/4] if_link.h: rebase to the kernel Jiri Benc
2016-04-07 12:36 ` [PATCH iproute2 2/4] vxlan: 'external' implies 'nolearning' Jiri Benc
2016-04-07 12:36 ` [PATCH iproute2 3/4] ip-link.8: document "external" flag for vxlan Jiri Benc
2016-04-07 12:36 ` [PATCH iproute2 4/4] vxlan: add support for VXLAN-GPE Jiri Benc
2016-04-11 22:17 ` Stephen Hemminger [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=20160411151754.6613c2f1@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=jbenc@redhat.com \
    --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