[Bridge] [PATCH v4 net-next 0/7] Offload software learnt bridge addresses to DSA

patchwork-bot+netdevbpf at kernel.org patchwork-bot+netdevbpf at kernel.org
Thu Jan 7 23:50:11 UTC 2021


This series was applied to netdev/net-next.git (refs/heads/master):

On Wed,  6 Jan 2021 11:51:29 +0200 you wrote:
> From: Vladimir Oltean <vladimir.oltean at nxp.com>
> This series tries to make DSA behave a bit more sanely when bridged with
> "foreign" (non-DSA) interfaces and source address learning is not
> supported on the hardware CPU port (which would make things work more
> seamlessly without software intervention). When a station A connected to
> a DSA switch port needs to talk to another station B connected to a
> non-DSA port through the Linux bridge, DSA must explicitly add a route
> for station B towards its CPU port.
> [...]

Here is the summary with links:
  - [v4,net-next,1/7] net: bridge: notify switchdev of disappearance of old FDB entry upon migration
  - [v4,net-next,2/7] net: dsa: be louder when a non-legacy FDB operation fails
  - [v4,net-next,3/7] net: dsa: don't use switchdev_notifier_fdb_info in dsa_switchdev_event_work
  - [v4,net-next,4/7] net: dsa: move switchdev event implementation under the same switch/case statement
  - [v4,net-next,5/7] net: dsa: exit early in dsa_slave_switchdev_event if we can't program the FDB
  - [v4,net-next,6/7] net: dsa: listen for SWITCHDEV_{FDB,DEL}_ADD_TO_DEVICE on foreign bridge neighbors
  - [v4,net-next,7/7] net: dsa: ocelot: request DSA to fix up lack of address learning on CPU port

You are awesome, thank you!
Deet-doot-dot, I am a bot.

More information about the Bridge mailing list