From: patchwork-bot+netdevbpf@kernel.org
To: Petr Machata <petrm@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
razor@blackwall.org, idosch@nvidia.com, bridge@lists.linux.dev,
yongwang@nvidia.com, aroulin@nvidia.com, mlxsw@nvidia.com
Subject: Re: [PATCH net-next 0/3] bridge: multicast: per vlan query improvement when port or vlan state changes
Date: Wed, 23 Apr 2025 12:10:31 +0000 [thread overview]
Message-ID: <174541023175.2604292.4001892845158453419.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1744896433.git.petrm@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 17 Apr 2025 15:43:11 +0200 you wrote:
> From: Yong Wang <yongwang@nvidia.com>
>
> The current implementation of br_multicast_enable_port() only operates on
> port's multicast context, which doesn't take into account in case of vlan
> snooping, one downside is the port's igmp query timer will NOT resume when
> port state gets changed from BR_STATE_BLOCKING to BR_STATE_FORWARDING etc.
>
> [...]
Here is the summary with links:
- [net-next,1/3] net: bridge: mcast: re-implement br_multicast_{enable, disable}_port functions
https://git.kernel.org/netdev/net-next/c/4b30ae9adb04
- [net-next,2/3] net: bridge: mcast: update multicast contex when vlan state is changed
https://git.kernel.org/netdev/net-next/c/6c131043eaf1
- [net-next,3/3] selftests: net/bridge : add tests for per vlan snooping with stp state changes
https://git.kernel.org/netdev/net-next/c/aea45363e29d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-04-23 12:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 13:43 [PATCH net-next 0/3] bridge: multicast: per vlan query improvement when port or vlan state changes Petr Machata
2025-04-17 13:43 ` [PATCH net-next 1/3] net: bridge: mcast: re-implement br_multicast_{enable, disable}_port functions Petr Machata
2025-04-19 6:38 ` Nikolay Aleksandrov
2025-04-19 14:33 ` Yong Wang
2025-04-22 12:20 ` Petr Machata
2025-04-17 13:43 ` [PATCH net-next 2/3] net: bridge: mcast: update multicast contex when vlan state is changed Petr Machata
2025-04-19 6:39 ` Nikolay Aleksandrov
2025-04-17 13:43 ` [PATCH net-next 3/3] selftests: net/bridge : add tests for per vlan snooping with stp state changes Petr Machata
2025-04-19 6:41 ` Nikolay Aleksandrov
2025-04-23 12:10 ` patchwork-bot+netdevbpf [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=174541023175.2604292.4001892845158453419.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aroulin@nvidia.com \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.org \
--cc=yongwang@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.