From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, razor@blackwall.org,
bridge@lists.linux-foundation.org, edumazet@google.com,
mlxsw@nvidia.com, roopa@nvidia.com, kuba@kernel.org,
pabeni@redhat.com, davem@davemloft.net
Subject: Re: [Bridge] [PATCH net-next v2 0/9] bridge: mcast: Preparations for EVPN extensions
Date: Thu, 08 Dec 2022 04:10:19 +0000 [thread overview]
Message-ID: <167047261955.18861.1757446402375104183.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221206105809.363767-1-idosch@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 6 Dec 2022 12:58:00 +0200 you wrote:
> This patchset was split from [1] and includes non-functional changes
> aimed at making it easier to add additional netlink attributes later on.
> Future extensions are available here [2].
>
> The idea behind these patches is to create an MDB configuration
> structure into which netlink messages are parsed into. The structure is
> then passed in the entry creation / deletion call chain instead of
> passing the netlink attributes themselves. The same pattern is used by
> other rtnetlink objects such as routes and nexthops.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/9] bridge: mcast: Centralize netlink attribute parsing
https://git.kernel.org/netdev/net-next/c/cb453926865e
- [net-next,v2,2/9] bridge: mcast: Remove redundant checks
https://git.kernel.org/netdev/net-next/c/386611681524
- [net-next,v2,3/9] bridge: mcast: Use MDB configuration structure where possible
https://git.kernel.org/netdev/net-next/c/f2b5aac68117
- [net-next,v2,4/9] bridge: mcast: Propagate MDB configuration structure further
https://git.kernel.org/netdev/net-next/c/8bd9c08e3241
- [net-next,v2,5/9] bridge: mcast: Use MDB group key from configuration structure
https://git.kernel.org/netdev/net-next/c/9f52a5142979
- [net-next,v2,6/9] bridge: mcast: Remove br_mdb_parse()
https://git.kernel.org/netdev/net-next/c/3ee5662345f2
- [net-next,v2,7/9] bridge: mcast: Move checks out of critical section
https://git.kernel.org/netdev/net-next/c/4c1ebc6c1f21
- [net-next,v2,8/9] bridge: mcast: Remove redundant function arguments
https://git.kernel.org/netdev/net-next/c/090149eaf391
- [net-next,v2,9/9] bridge: mcast: Constify 'group' argument in br_multicast_new_port_group()
https://git.kernel.org/netdev/net-next/c/f86c3e2c1b5e
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:[~2022-12-08 4:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 10:58 [Bridge] [PATCH net-next v2 0/9] bridge: mcast: Preparations for EVPN extensions Ido Schimmel
2022-12-06 10:58 ` [Bridge] [PATCH net-next v2 1/9] bridge: mcast: Centralize netlink attribute parsing Ido Schimmel
2022-12-06 12:32 ` Nikolay Aleksandrov
2022-12-06 10:58 ` [Bridge] [PATCH net-next v2 2/9] bridge: mcast: Remove redundant checks Ido Schimmel
2022-12-06 10:58 ` [Bridge] [PATCH net-next v2 3/9] bridge: mcast: Use MDB configuration structure where possible Ido Schimmel
2022-12-06 10:58 ` [Bridge] [PATCH net-next v2 4/9] bridge: mcast: Propagate MDB configuration structure further Ido Schimmel
2022-12-06 10:58 ` [Bridge] [PATCH net-next v2 5/9] bridge: mcast: Use MDB group key from configuration structure Ido Schimmel
2022-12-06 10:58 ` [Bridge] [PATCH net-next v2 6/9] bridge: mcast: Remove br_mdb_parse() Ido Schimmel
2022-12-06 10:58 ` [Bridge] [PATCH net-next v2 7/9] bridge: mcast: Move checks out of critical section Ido Schimmel
2022-12-06 10:58 ` [Bridge] [PATCH net-next v2 8/9] bridge: mcast: Remove redundant function arguments Ido Schimmel
2022-12-06 10:58 ` [Bridge] [PATCH net-next v2 9/9] bridge: mcast: Constify 'group' argument in br_multicast_new_port_group() Ido Schimmel
2022-12-06 12:32 ` Nikolay Aleksandrov
2022-12-08 4: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=167047261955.18861.1757446402375104183.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox