From: David Ahern <dsa@cumulusnetworks.com>
To: Alexis Bauvin <abauvin@scaleway.com>, roopa@cumulusnetworks.com
Cc: netdev@vger.kernel.org, akherbouche@scaleway.com
Subject: Re: [RFC v3 3/3] vxlan: handle underlay VRF changes
Date: Tue, 20 Nov 2018 09:54:26 -0700 [thread overview]
Message-ID: <b9ffc242-d522-2d5c-627b-24c23d58d6d4@cumulusnetworks.com> (raw)
In-Reply-To: <A40461AE-44D0-436D-BAA7-A90A05166CE1@scaleway.com>
On 11/20/18 9:27 AM, Alexis Bauvin wrote:
> maybe even move
> the function to net/core/dev.c, with other master-related functions.
> What do you think?
yes, it is a generic function.
next prev parent reply other threads:[~2018-11-21 3:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 14:23 [RFC v3 0/3] Add VRF support for VXLAN underlay Alexis Bauvin
2018-11-20 14:23 ` [RFC v3 1/3] udp_tunnel: add config option to bind to a device Alexis Bauvin
2018-11-20 14:23 ` [RFC v3 2/3] vxlan: add support for underlay in non-default VRF Alexis Bauvin
2018-11-20 14:57 ` David Ahern
2018-11-20 16:11 ` Alexis Bauvin
2018-11-20 15:25 ` Roopa Prabhu
2018-11-20 16:14 ` Alexis Bauvin
2018-11-20 14:23 ` [RFC v3 3/3] vxlan: handle underlay VRF changes Alexis Bauvin
2018-11-20 15:04 ` David Ahern
2018-11-20 15:35 ` Roopa Prabhu
2018-11-20 15:48 ` David Ahern
2018-11-20 16:13 ` David Ahern
2018-11-20 18:19 ` Alexis Bauvin
2018-11-20 16:58 ` Alexis Bauvin
2018-11-20 17:09 ` David Ahern
2018-11-21 14:05 ` Alexis Bauvin
2018-11-21 19:28 ` David Ahern
2018-11-22 0:54 ` Alexis Bauvin
2018-11-22 1:48 ` David Ahern
2018-11-20 16:27 ` Alexis Bauvin
2018-11-20 16:54 ` David Ahern [this message]
2018-11-20 14:48 ` [RFC v3 0/3] Add VRF support for VXLAN underlay David Ahern
2018-11-20 21:45 ` David Ahern
2018-11-21 13:30 ` Alexis Bauvin
2018-11-21 19:26 ` David Ahern
2018-11-22 0:47 ` Alexis Bauvin
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=b9ffc242-d522-2d5c-627b-24c23d58d6d4@cumulusnetworks.com \
--to=dsa@cumulusnetworks.com \
--cc=abauvin@scaleway.com \
--cc=akherbouche@scaleway.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.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