From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <olteanv@gmail.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
andrew@lunn.ch, f.fainelli@gmail.com, vivien.didelot@gmail.com,
jiri@resnulli.us, idosch@idosch.org, tobias@waldekranz.com,
roopa@nvidia.com, nikolay@nvidia.com,
bridge@lists.linux-foundation.org, vladimir.oltean@nxp.com
Subject: Re: [PATCH v5 net-next 00/15] RX filtering in DSA
Date: Tue, 29 Jun 2021 17:50:06 +0000 [thread overview]
Message-ID: <162498900637.32370.6838402243574308383.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210629140658.2510288-1-olteanv@gmail.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Tue, 29 Jun 2021 17:06:43 +0300 you wrote:
> From: Vladimir Oltean <vladimir.oltean@nxp.com>
>
> This is my 5th stab at creating a list of unicast and multicast
> addresses that the DSA CPU ports must trap. I am reusing a lot of
> Tobias's work which he submitted here:
> https://patchwork.kernel.org/project/netdevbpf/cover/20210116012515.3152-1-tobias@waldekranz.com/
>
> [...]
Here is the summary with links:
- [v5,net-next,01/15] net: bridge: use READ_ONCE() and WRITE_ONCE() compiler barriers for fdb->dst
https://git.kernel.org/netdev/net-next/c/3e19ae7c6fd6
- [v5,net-next,02/15] net: bridge: switchdev: send FDB notifications for host addresses
https://git.kernel.org/netdev/net-next/c/6eb38bf8eb90
- [v5,net-next,03/15] net: bridge: allow br_fdb_replay to be called for the bridge device
https://git.kernel.org/netdev/net-next/c/f851a721a638
- [v5,net-next,04/15] net: dsa: delete dsa_legacy_fdb_add and dsa_legacy_fdb_del
https://git.kernel.org/netdev/net-next/c/b117e1e8a86d
- [v5,net-next,05/15] net: dsa: introduce dsa_is_upstream_port and dsa_switch_is_upstream_of
https://git.kernel.org/netdev/net-next/c/63609c8fac40
- [v5,net-next,06/15] net: dsa: introduce a separate cross-chip notifier type for host MDBs
https://git.kernel.org/netdev/net-next/c/b8e997c49003
- [v5,net-next,07/15] net: dsa: reference count the MDB entries at the cross-chip notifier level
https://git.kernel.org/netdev/net-next/c/161ca59d39e9
- [v5,net-next,08/15] net: dsa: introduce a separate cross-chip notifier type for host FDBs
https://git.kernel.org/netdev/net-next/c/3dc80afc5098
- [v5,net-next,09/15] net: dsa: reference count the FDB addresses at the cross-chip notifier level
https://git.kernel.org/netdev/net-next/c/3f6e32f92a02
- [v5,net-next,10/15] net: dsa: install the host MDB and FDB entries in the master's RX filter
https://git.kernel.org/netdev/net-next/c/26ee7b06a4d3
- [v5,net-next,11/15] net: dsa: sync static FDB entries on foreign interfaces to hardware
https://git.kernel.org/netdev/net-next/c/3068d466a67e
- [v5,net-next,12/15] net: dsa: include bridge addresses which are local in the host fdb list
https://git.kernel.org/netdev/net-next/c/10fae4ac89ce
- [v5,net-next,13/15] net: dsa: include fdb entries pointing to bridge in the host fdb list
https://git.kernel.org/netdev/net-next/c/81a619f78759
- [v5,net-next,14/15] net: dsa: ensure during dsa_fdb_offload_notify that dev_hold and dev_put are on the same dev
https://git.kernel.org/netdev/net-next/c/4bed397c3e65
- [v5,net-next,15/15] net: dsa: replay the local bridge FDB entries pointing to the bridge dev too
https://git.kernel.org/netdev/net-next/c/63c51453c82c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-06-29 17:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 14:06 [PATCH v5 net-next 00/15] RX filtering in DSA Vladimir Oltean
2021-06-29 14:06 ` [PATCH v5 net-next 01/15] net: bridge: use READ_ONCE() and WRITE_ONCE() compiler barriers for fdb->dst Vladimir Oltean
2021-06-29 14:06 ` [PATCH v5 net-next 02/15] net: bridge: switchdev: send FDB notifications for host addresses Vladimir Oltean
2021-06-29 14:06 ` [PATCH v5 net-next 03/15] net: bridge: allow br_fdb_replay to be called for the bridge device Vladimir Oltean
2021-06-29 14:06 ` [PATCH v5 net-next 04/15] net: dsa: delete dsa_legacy_fdb_add and dsa_legacy_fdb_del Vladimir Oltean
2021-06-29 14:06 ` [PATCH v5 net-next 05/15] net: dsa: introduce dsa_is_upstream_port and dsa_switch_is_upstream_of Vladimir Oltean
2021-06-29 14:06 ` [PATCH v5 net-next 06/15] net: dsa: introduce a separate cross-chip notifier type for host MDBs Vladimir Oltean
2021-06-29 14:06 ` [PATCH v5 net-next 07/15] net: dsa: reference count the MDB entries at the cross-chip notifier level Vladimir Oltean
2021-06-29 14:06 ` [PATCH v5 net-next 08/15] net: dsa: introduce a separate cross-chip notifier type for host FDBs Vladimir Oltean
2021-06-29 14:06 ` [PATCH v5 net-next 09/15] net: dsa: reference count the FDB addresses at the cross-chip notifier level Vladimir Oltean
2021-06-29 14:06 ` [PATCH v5 net-next 10/15] net: dsa: install the host MDB and FDB entries in the master's RX filter Vladimir Oltean
2021-06-29 14:06 ` [PATCH v5 net-next 11/15] net: dsa: sync static FDB entries on foreign interfaces to hardware Vladimir Oltean
2021-06-29 14:06 ` [PATCH v5 net-next 12/15] net: dsa: include bridge addresses which are local in the host fdb list Vladimir Oltean
2021-06-29 14:06 ` [PATCH v5 net-next 13/15] net: dsa: include fdb entries pointing to bridge " Vladimir Oltean
2021-06-29 14:06 ` [PATCH v5 net-next 14/15] net: dsa: ensure during dsa_fdb_offload_notify that dev_hold and dev_put are on the same dev Vladimir Oltean
2021-06-29 14:06 ` [PATCH v5 net-next 15/15] net: dsa: replay the local bridge FDB entries pointing to the bridge dev too Vladimir Oltean
2021-06-29 17:50 ` patchwork-bot+netdevbpf [this message]
2021-06-29 18:52 ` [PATCH v5 net-next 00/15] RX filtering in DSA David Miller
2021-06-29 18:58 ` Vladimir Oltean
2021-06-29 19:09 ` Vladimir Oltean
2021-06-29 22:08 ` David Miller
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=162498900637.32370.6838402243574308383.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=idosch@idosch.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=olteanv@gmail.com \
--cc=roopa@nvidia.com \
--cc=tobias@waldekranz.com \
--cc=vivien.didelot@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).