From: David Miller <davem@davemloft.net>
To: roopa@cumulusnetworks.com
Cc: netdev@vger.kernel.org, jbenc@redhat.com,
hannes@stressinduktion.org, nicolas.dichtel@6wind.com,
nikolay@cumulusnetworks.com
Subject: Re: [PATCH net-next] vxlan: dont migrate permanent fdb entries during learn
Date: Sun, 11 Jun 2017 19:04:16 -0400 (EDT) [thread overview]
Message-ID: <20170611.190416.1443081184910537296.davem@davemloft.net> (raw)
In-Reply-To: <1497221482-33473-1-git-send-email-roopa@cumulusnetworks.com>
From: Roopa Prabhu <roopa@cumulusnetworks.com>
Date: Sun, 11 Jun 2017 15:51:22 -0700
> From: Roopa Prabhu <roopa@cumulusnetworks.com>
>
> This patch fixes vxlan_snoop to not move permanent fdb entries
> on learn events. This is consistent with the bridge fdb
> handling of permanent entries.
>
> Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com>
Is there an appropriate Fixes: tag by chance?
next prev parent reply other threads:[~2017-06-11 23:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-11 22:51 [PATCH net-next] vxlan: dont migrate permanent fdb entries during learn Roopa Prabhu
2017-06-11 23:04 ` David Miller [this message]
2017-06-11 23:26 ` Roopa Prabhu
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=20170611.190416.1443081184910537296.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=jbenc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=nikolay@cumulusnetworks.com \
--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