From: Nikolay Aleksandrov <nikolay@cumulusnetworks•com>
To: David Miller <davem@davemloft•net>
Cc: netdev@vger•kernel.org, bridge@lists•linux-foundation.org,
herbert@gondor•apana.org.au, stephen@networkplumber•org,
sashok@cumulusnetworks•com
Subject: Re: [PATCH net-next 0/2] bridge: multicast: temp and perm entries behaviour enhancements
Date: Mon, 20 Jul 2015 22:35:50 +0200 [thread overview]
Message-ID: <55AD5BA6.3050101@cumulusnetworks.com> (raw)
In-Reply-To: <20150720.124939.1328394717828737521.davem@davemloft.net>
On 07/20/2015 09:49 PM, David Miller wrote:
> From: Nikolay Aleksandrov <nikolay@cumulusnetworks•com>
> Date: Wed, 15 Jul 2015 07:16:49 -0700
>
>> Hi,
>> Patch 01 adds a notify when a group is deleted via br_multicast_del_pg()
>> (on expire, on device delete or on device down).
>> Patch 02 changes how bridge device and bridge port delete and down/up are
>> handled. Until now on bridge down all groups were flushed, now only the
>> temp ones are (same for port), perm entries are flushed only on port or
>> bridge removal.
>
> Series applied, but if patch #2 breaks things for anyone depending upon the
> old behavior of flushing all entries I will have to revert.
>
Okay, understood.
prev parent reply other threads:[~2015-07-20 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 14:16 [PATCH net-next 0/2] bridge: multicast: temp and perm entries behaviour enhancements Nikolay Aleksandrov
2015-07-15 14:16 ` [PATCH net-next 1/2] bridge: multicast: notify on group delete Nikolay Aleksandrov
2015-07-15 14:16 ` [PATCH net-next 2/2] bridge: multicast: fix handling of temp and perm entries Nikolay Aleksandrov
2015-07-20 19:49 ` [PATCH net-next 0/2] bridge: multicast: temp and perm entries behaviour enhancements David Miller
2015-07-20 20:35 ` Nikolay Aleksandrov [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=55AD5BA6.3050101@cumulusnetworks.com \
--to=nikolay@cumulusnetworks$(echo .)com \
--cc=bridge@lists$(echo .)linux-foundation.org \
--cc=davem@davemloft$(echo .)net \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sashok@cumulusnetworks$(echo .)com \
--cc=stephen@networkplumber$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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