From: patchwork-bot+netdevbpf@kernel.org
To: Joseph Huang <Joseph.Huang@garmin.com>
Cc: netdev@vger.kernel.org, joseph.huang.2024@gmail.com,
razor@blackwall.org, idosch@nvidia.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, vladimir.oltean@nxp.com, f.fainelli@gmail.com,
tobias@waldekranz.com, bridge@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 net] net: bridge: Do not offload IGMP/MLD messages
Date: Thu, 17 Jul 2025 14:50:25 +0000 [thread overview]
Message-ID: <175276382500.1959085.4099760417199249498.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250716153551.1830255-1-Joseph.Huang@garmin.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 16 Jul 2025 11:35:50 -0400 you wrote:
> Do not offload IGMP/MLD messages as it could lead to IGMP/MLD Reports
> being unintentionally flooded to Hosts. Instead, let the bridge decide
> where to send these IGMP/MLD messages.
>
> Consider the case where the local host is sending out reports in response
> to a remote querier like the following:
>
> [...]
Here is the summary with links:
- [v3,net] net: bridge: Do not offload IGMP/MLD messages
https://git.kernel.org/netdev/net/c/683dc24da8bf
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-07-17 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 15:35 [PATCH v3 net] net: bridge: Do not offload IGMP/MLD messages Joseph Huang
2025-07-16 15:42 ` Nikolay Aleksandrov
2025-07-16 15:57 ` Ido Schimmel
2025-07-17 14:50 ` 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=175276382500.1959085.4099760417199249498.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Joseph.Huang@garmin.com \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=joseph.huang.2024@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=tobias@waldekranz.com \
--cc=vladimir.oltean@nxp.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.