From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <olteanv@gmail.com>
Cc: andrew@lunn.ch, vivien.didelot@gmail.com, f.fainelli@gmail.com,
kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, bridge@lists.linux-foundation.org,
roopa@nvidia.com, nikolay@nvidia.com, davem@davemloft.net,
dqfext@gmail.com, tobias@waldekranz.com, marek.behun@nic.cz,
linux@armlinux.org.uk, wintera@linux.ibm.com, jiri@resnulli.us,
idosch@idosch.org, claudiu.manoil@nxp.com,
UNGLinuxDriver@microchip.com
Subject: Re: [PATCH v4 net-next 0/7] Offload software learnt bridge addresses to DSA
Date: Thu, 07 Jan 2021 23:50:11 +0000 [thread overview]
Message-ID: <161006341107.8293.17599601765854120224.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210106095136.224739-1-olteanv@gmail.com>
Hello:
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@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
https://git.kernel.org/netdev/net-next/c/90dc8fd36078
- [v4,net-next,2/7] net: dsa: be louder when a non-legacy FDB operation fails
https://git.kernel.org/netdev/net-next/c/2fd186501b1c
- [v4,net-next,3/7] net: dsa: don't use switchdev_notifier_fdb_info in dsa_switchdev_event_work
https://git.kernel.org/netdev/net-next/c/c4bb76a9a0ef
- [v4,net-next,4/7] net: dsa: move switchdev event implementation under the same switch/case statement
https://git.kernel.org/netdev/net-next/c/447d290a58bd
- [v4,net-next,5/7] net: dsa: exit early in dsa_slave_switchdev_event if we can't program the FDB
https://git.kernel.org/netdev/net-next/c/5fb4a451a87d
- [v4,net-next,6/7] net: dsa: listen for SWITCHDEV_{FDB,DEL}_ADD_TO_DEVICE on foreign bridge neighbors
https://git.kernel.org/netdev/net-next/c/d5f19486cee7
- [v4,net-next,7/7] net: dsa: ocelot: request DSA to fix up lack of address learning on CPU port
https://git.kernel.org/netdev/net-next/c/c54913c1d4ee
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-01-07 23:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 9:51 [PATCH v4 net-next 0/7] Offload software learnt bridge addresses to DSA Vladimir Oltean
2021-01-06 9:51 ` [PATCH v4 net-next 1/7] net: bridge: notify switchdev of disappearance of old FDB entry upon migration Vladimir Oltean
2021-01-06 17:43 ` Florian Fainelli
2021-01-06 9:51 ` [PATCH v4 net-next 2/7] net: dsa: be louder when a non-legacy FDB operation fails Vladimir Oltean
2021-01-06 17:44 ` Florian Fainelli
2021-01-06 9:51 ` [PATCH v4 net-next 3/7] net: dsa: don't use switchdev_notifier_fdb_info in dsa_switchdev_event_work Vladimir Oltean
2021-01-06 9:51 ` [PATCH v4 net-next 4/7] net: dsa: move switchdev event implementation under the same switch/case statement Vladimir Oltean
2021-01-06 9:51 ` [PATCH v4 net-next 5/7] net: dsa: exit early in dsa_slave_switchdev_event if we can't program the FDB Vladimir Oltean
2021-01-06 9:51 ` [PATCH v4 net-next 6/7] net: dsa: listen for SWITCHDEV_{FDB,DEL}_ADD_TO_DEVICE on foreign bridge neighbors Vladimir Oltean
2021-01-06 9:51 ` [PATCH v4 net-next 7/7] net: dsa: ocelot: request DSA to fix up lack of address learning on CPU port Vladimir Oltean
2021-01-07 23:50 ` 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=161006341107.8293.17599601765854120224.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=bridge@lists.linux-foundation.org \
--cc=claudiu.manoil@nxp.com \
--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=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marek.behun@nic.cz \
--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=wintera@linux.ibm.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).