From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.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, stephen@networkplumber.org,
bridge@lists.linux-foundation.org, dqfext@gmail.com
Subject: Re: [PATCH net-next 0/3] Fan out FDB entries pointing towards the bridge to all switchdev member ports
Date: Tue, 20 Jul 2021 14:10:05 +0000 [thread overview]
Message-ID: <162679020560.11280.5860965048088740851.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210719135140.278938-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Mon, 19 Jul 2021 16:51:37 +0300 you wrote:
> The "DSA RX filtering" series has added some important support for
> interpreting addresses towards the bridge device as host addresses and
> installing them as FDB entries towards the CPU port, but it does not
> cover all circumstances and needs further work.
>
> To be precise, the mechanism introduced in that series only works as
> long as the ports are fairly static and no port joins or leaves the
> bridge once the configuration is done. If any port leaves, host FDB
> entries that were installed during runtime (for example the user changes
> the MAC address of the bridge device) will be prematurely deleted,
> resulting in a broken setup.
>
> [...]
Here is the summary with links:
- [net-next,1/3] net: switchdev: introduce helper for checking dynamically learned FDB entries
https://git.kernel.org/netdev/net-next/c/c6451cda100d
- [net-next,2/3] net: switchdev: introduce a fanout helper for SWITCHDEV_FDB_{ADD,DEL}_TO_DEVICE
https://git.kernel.org/netdev/net-next/c/8ca07176ab00
- [net-next,3/3] net: dsa: use switchdev_handle_fdb_{add,del}_to_device
https://git.kernel.org/netdev/net-next/c/b94dc99c0ddb
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:[~2021-07-20 14:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 13:51 [PATCH net-next 0/3] Fan out FDB entries pointing towards the bridge to all switchdev member ports Vladimir Oltean
2021-07-19 13:51 ` [PATCH net-next 1/3] net: switchdev: introduce helper for checking dynamically learned FDB entries Vladimir Oltean
2021-07-19 13:51 ` [PATCH net-next 2/3] net: switchdev: introduce a fanout helper for SWITCHDEV_FDB_{ADD,DEL}_TO_DEVICE Vladimir Oltean
2021-07-19 13:51 ` [PATCH net-next 3/3] net: dsa: use switchdev_handle_fdb_{add,del}_to_device Vladimir Oltean
2021-07-20 14: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=162679020560.11280.5860965048088740851.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=dqfext@gmail.com \
--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=roopa@nvidia.com \
--cc=stephen@networkplumber.org \
--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).