From: patchwork-bot+netdevbpf@kernel.org
To: Petr Machata <petrm@nvidia.com>
Cc: netdev@vger.kernel.org, dsahern@gmail.com,
stephen@networkplumber.org, razor@blackwall.org,
idosch@nvidia.com
Subject: Re: [PATCH iproute2-next v2 0/3] bridge: Support mcast_n_groups, mcast_max_groups
Date: Tue, 07 Feb 2023 16:20:18 +0000 [thread overview]
Message-ID: <167578681852.1661.11842550127865456255.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1675765297.git.petrm@nvidia.com>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Tue, 7 Feb 2023 11:27:47 +0100 you wrote:
> In the Linux kernel commit cb3086cee656 ("Merge branch
> 'bridge-mdb-limit'"), the bridge driver gained support for limiting number
> of MDB entries that a given port or port-VLAN is a member of. Support these
> new attributes in iproute2's bridge tool.
>
> After syncing the two relevant headers in patch #1, patch #2 introduces the
> meat of the support, and patch #3 the man page coverage.
>
> [...]
Here is the summary with links:
- [iproute2-next,v2,1/3] uapi: Update if_bridge, if_link
(no matching commit)
- [iproute2-next,v2,2/3] bridge: Add support for mcast_n_groups, mcast_max_groups
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=4300ee77e807
- [iproute2-next,v2,3/3] man: man8: bridge: Describe mcast_max_groups
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=b96b06830fe1
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:[~2023-02-07 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 10:27 [PATCH iproute2-next v2 0/3] bridge: Support mcast_n_groups, mcast_max_groups Petr Machata
2023-02-07 10:27 ` [PATCH iproute2-next v2 1/3] uapi: Update if_bridge, if_link Petr Machata
2023-02-07 10:27 ` [PATCH iproute2-next v2 2/3] bridge: Add support for mcast_n_groups, mcast_max_groups Petr Machata
2023-02-07 10:27 ` [PATCH iproute2-next v2 3/3] man: man8: bridge: Describe mcast_max_groups Petr Machata
2023-02-07 16:20 ` 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=167578681852.1661.11842550127865456255.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@gmail.com \
--cc=idosch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.org \
--cc=stephen@networkplumber.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.