From: William Dauchy <w.dauchy@criteo.com>
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: William Dauchy <w.dauchy@criteo.com>, NETDEV <netdev@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] net, ip6_tunnel: enhance tunnel locate with type check
Date: Wed, 5 Feb 2020 18:31:41 +0100 [thread overview]
Message-ID: <CAJ75kXbS6AU6fLhVbKbvDBhN9-o3L94NsNcywROjU1bH0U4j+w@mail.gmail.com> (raw)
In-Reply-To: <d9913ff8-988a-0c24-d614-ff59815bf6d7@6wind.com>
On Wed, Feb 5, 2020 at 6:01 PM Nicolas Dichtel
<nicolas.dichtel@6wind.com> wrote:
> Can you elaborate? What problem does this solve?
> Which tree are you targeting? net or net-next?
I was seeing that as a nice to have for coherency between ip6_tunnel
and ip_tunnel. But we can drop this one if we lack of practical
example, as I was more concerned about link check in the 1/2 patch.
It was more for net in my opinion as I considered it not too invasive.
--
William
next prev parent reply other threads:[~2020-02-05 17:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 14:57 [PATCH] net, ip6_tunnel: enhance tunnel locate with link/type check William Dauchy
2020-02-05 15:04 ` Nicolas Dichtel
2020-02-05 16:29 ` [PATCH v2 0/2] net, ip6_tunnel: enhance tunnel locate William Dauchy
2020-02-05 16:29 ` [PATCH v2 1/2] net, ip6_tunnel: enhance tunnel locate with link check William Dauchy
2020-02-05 16:54 ` Nicolas Dichtel
2020-02-05 17:36 ` William Dauchy
2020-02-12 8:30 ` [PATCH v3 net] " William Dauchy
2020-02-12 15:54 ` Nicolas Dichtel
2020-02-12 21:06 ` William Dauchy
2020-02-13 9:34 ` Nicolas Dichtel
2020-02-13 15:26 ` William Dauchy
2020-02-13 15:35 ` [PATCH v4 " William Dauchy
2020-02-13 16:33 ` Nicolas Dichtel
2020-02-13 17:19 ` [PATCH v5 " William Dauchy
2020-02-14 9:50 ` Nicolas Dichtel
2020-02-14 15:32 ` David Miller
2020-02-05 16:29 ` [PATCH v2 2/2] net, ip6_tunnel: enhance tunnel locate with type check William Dauchy
2020-02-05 16:59 ` Nicolas Dichtel
2020-02-05 17:31 ` William Dauchy [this message]
2020-02-05 18:16 ` William Dauchy
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=CAJ75kXbS6AU6fLhVbKbvDBhN9-o3L94NsNcywROjU1bH0U4j+w@mail.gmail.com \
--to=w.dauchy@criteo.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
/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).