From: patchwork-bot+netdevbpf@kernel.org
To: Fabian Pfitzner <f.pfitzner@pengutronix.de>
Cc: netdev@vger.kernel.org, entwicklung@pengutronix.de,
razor@blackwall.org, bridge@lists.linux-foundation.org,
dsahern@gmail.com, idosch@nvidia.com
Subject: Re: [PATCH iproute2-next v6 0/3] bridge: dump mcast querier state per vlan
Date: Wed, 02 Jul 2025 14:40:10 +0000 [thread overview]
Message-ID: <175146721025.744720.14595669667124615372.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250625-mcast-querier-vlan-lib-v6-0-03659be44d48@pengutronix.de>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Wed, 25 Jun 2025 10:39:12 +0200 you wrote:
> Dump the multicast querier state per vlan.
> This commit is almost identical to [1].
>
> The querier state can be seen with:
>
> bridge -d vlan global
>
> [...]
Here is the summary with links:
- [iproute2-next,v6,1/3] bridge: move mcast querier dumping code into a shared function
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=da6fbcf63c13
- [iproute2-next,v6,2/3] bridge: dump mcast querier per vlan
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=baeeb9a8e184
- [iproute2-next,v6,3/3] bridge: refactor bridge mcast querier function
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=cdc027cb7f47
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-02 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 8:39 [PATCH iproute2-next v6 0/3] bridge: dump mcast querier state per vlan Fabian Pfitzner
2025-06-25 8:39 ` [PATCH iproute2-next v6 1/3] bridge: move mcast querier dumping code into a shared function Fabian Pfitzner
2025-06-25 8:39 ` [PATCH iproute2-next v6 2/3] bridge: dump mcast querier per vlan Fabian Pfitzner
2025-06-25 8:39 ` [PATCH iproute2-next v6 3/3] bridge: refactor bridge mcast querier function Fabian Pfitzner
2025-07-02 14:40 ` 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=175146721025.744720.14595669667124615372.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bridge@lists.linux-foundation.org \
--cc=dsahern@gmail.com \
--cc=entwicklung@pengutronix.de \
--cc=f.pfitzner@pengutronix.de \
--cc=idosch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
/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.