All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Andrea Claudi <aclaudi@redhat.com>
Cc: netdev@vger.kernel.org, dsahern@kernel.org
Subject: Re: [PATCH iproute2 0/2] Fix IPv6 tunnel add when dev param is used
Date: Tue, 16 Jul 2019 12:28:17 -0700	[thread overview]
Message-ID: <20190716122817.43d644cf@hermes.lan> (raw)
In-Reply-To: <cover.1562667648.git.aclaudi@redhat.com>

On Tue,  9 Jul 2019 15:16:49 +0200
Andrea Claudi <aclaudi@redhat.com> wrote:

> Commit ba126dcad20e6 ("ip6tunnel: fix 'ip -6 {show|change} dev
> <name>' cmds") breaks IPv6 tunnel creation when dev parameter
> is used.
> 
> This series revert the original commit, which mistakenly use
> dev for tunnel name, while addressing a issue on tunnel change
> when no interface name is specified.
> 
> Andrea Claudi (2):
>   Revert "ip6tunnel: fix 'ip -6 {show|change} dev <name>' cmds"
>   ip tunnel: warn when changing IPv6 tunnel without tunnel name
> 
>  ip/ip6tunnel.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 

Both applied, thanks

      parent reply	other threads:[~2019-07-16 19:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-09 13:16 [PATCH iproute2 0/2] Fix IPv6 tunnel add when dev param is used Andrea Claudi
2019-07-09 13:16 ` [PATCH iproute2 1/2] Revert "ip6tunnel: fix 'ip -6 {show|change} dev <name>' cmds" Andrea Claudi
2019-07-09 17:14   ` David Ahern
2019-07-09 17:39     ` Stephen Hemminger
2019-07-09 17:31   ` Mahesh Bandewar (महेश बंडेवार)
2019-07-10 10:11     ` Andrea Claudi
2019-07-09 13:16 ` [PATCH iproute2 2/2] ip tunnel: warn when changing IPv6 tunnel without tunnel name Andrea Claudi
2019-07-09 22:14   ` Mahesh Bandewar (महेश बंडेवार)
2019-07-10  8:33     ` Andrea Claudi
2019-07-16 19:28 ` 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=20190716122817.43d644cf@hermes.lan \
    --to=stephen@networkplumber.org \
    --cc=aclaudi@redhat.com \
    --cc=dsahern@kernel.org \
    --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 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.