From: patchwork-bot+netdevbpf@kernel.org
To: Nikolay Aleksandrov <nikolay@nvidia.com>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
davem@davemloft.net, kuba@kernel.org, roopa@nvidia.com
Subject: Re: [Bridge] [PATCH net v2] net: bridge: mcast: fix br_multicast_ctx_vlan_global_disabled helper
Date: Thu, 30 Dec 2021 02:00:11 +0000 [thread overview]
Message-ID: <164082961129.30206.7745851458626854957.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211228153142.536969-1-nikolay@nvidia.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 28 Dec 2021 17:31:42 +0200 you wrote:
> We need to first check if the context is a vlan one, then we need to
> check the global bridge multicast vlan snooping flag, and finally the
> vlan's multicast flag, otherwise we will unnecessarily enable vlan mcast
> processing (e.g. querier timers).
>
> Fixes: 7b54aaaf53cb ("net: bridge: multicast: add vlan state initialization and control")
> Signed-off-by: Nikolay Aleksandrov <nikolay@nvidia.com>
>
> [...]
Here is the summary with links:
- [net,v2] net: bridge: mcast: fix br_multicast_ctx_vlan_global_disabled helper
https://git.kernel.org/netdev/net/c/168fed986b3a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Nikolay Aleksandrov <nikolay@nvidia.com>
Cc: netdev@vger.kernel.org, roopa@nvidia.com, davem@davemloft.net,
bridge@lists.linux-foundation.org, kuba@kernel.org
Subject: Re: [PATCH net v2] net: bridge: mcast: fix br_multicast_ctx_vlan_global_disabled helper
Date: Thu, 30 Dec 2021 02:00:11 +0000 [thread overview]
Message-ID: <164082961129.30206.7745851458626854957.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211228153142.536969-1-nikolay@nvidia.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 28 Dec 2021 17:31:42 +0200 you wrote:
> We need to first check if the context is a vlan one, then we need to
> check the global bridge multicast vlan snooping flag, and finally the
> vlan's multicast flag, otherwise we will unnecessarily enable vlan mcast
> processing (e.g. querier timers).
>
> Fixes: 7b54aaaf53cb ("net: bridge: multicast: add vlan state initialization and control")
> Signed-off-by: Nikolay Aleksandrov <nikolay@nvidia.com>
>
> [...]
Here is the summary with links:
- [net,v2] net: bridge: mcast: fix br_multicast_ctx_vlan_global_disabled helper
https://git.kernel.org/netdev/net/c/168fed986b3a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-12-30 2:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 15:28 [Bridge] [PATCH net] net: bridge: mcast: fix br_multicast_ctx_vlan_global_disabled helper Nikolay Aleksandrov
2021-12-28 15:28 ` Nikolay Aleksandrov
2021-12-28 15:31 ` [Bridge] [PATCH net v2] " Nikolay Aleksandrov
2021-12-28 15:31 ` Nikolay Aleksandrov
2021-12-30 2:00 ` patchwork-bot+netdevbpf [this message]
2021-12-30 2:00 ` patchwork-bot+netdevbpf
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=164082961129.30206.7745851458626854957.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=roopa@nvidia.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 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.