From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
pabeni@redhat.com, edumazet@google.com, f.fainelli@gmail.com,
vivien.didelot@gmail.com, andrew@lunn.ch, olteanv@gmail.com,
tobias@waldekranz.com, kabel@kernel.org, ansuelsmth@gmail.com,
dqfext@gmail.com, alsi@bang-olufsen.dk, claudiu.manoil@nxp.com,
alexandre.belloni@bootlin.com, UNGLinuxDriver@microchip.com,
colin.foster@in-advantage.com, linus.walleij@linaro.org,
luizluca@gmail.com
Subject: Re: [PATCH v2 net-next 0/8] DSA changes for multiple CPU ports (part 1)
Date: Thu, 12 May 2022 23:50:14 +0000 [thread overview]
Message-ID: <165239941497.20203.10953892440196302945.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220511095020.562461-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 11 May 2022 12:50:12 +0300 you wrote:
> I am trying to enable the second internal port pair from the NXP LS1028A
> Felix switch for DSA-tagged traffic via "ocelot-8021q". This series
> represents part 1 (of an unknown number) of that effort.
>
> It does some preparation work, like managing host flooding in DSA via a
> dedicated method, and removing the CPU port as argument from the tagging
> protocol change procedure.
>
> [...]
Here is the summary with links:
- [v2,net-next,1/8] net: dsa: felix: program host FDB entries towards PGID_CPU for tag_8021q too
https://git.kernel.org/netdev/net-next/c/e9b3ba439dcb
- [v2,net-next,2/8] net: dsa: felix: bring the NPI port indirection for host MDBs to surface
https://git.kernel.org/netdev/net-next/c/0ddf83cda5a6
- [v2,net-next,3/8] net: dsa: felix: bring the NPI port indirection for host flooding to surface
https://git.kernel.org/netdev/net-next/c/910ee6cce92f
- [v2,net-next,4/8] net: dsa: introduce the dsa_cpu_ports() helper
https://git.kernel.org/netdev/net-next/c/465c3de42b5d
- [v2,net-next,5/8] net: dsa: felix: manage host flooding using a specific driver callback
https://git.kernel.org/netdev/net-next/c/72c3b0c7359a
- [v2,net-next,6/8] net: dsa: remove port argument from ->change_tag_protocol()
https://git.kernel.org/netdev/net-next/c/bacf93b05619
- [v2,net-next,7/8] net: dsa: felix: dynamically determine tag_8021q CPU port for traps
https://git.kernel.org/netdev/net-next/c/c352e5e8e8f2
- [v2,net-next,8/8] net: dsa: felix: reimplement tagging protocol change with function pointers
https://git.kernel.org/netdev/net-next/c/7a29d220f4c0
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-05-12 23:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 9:50 [PATCH v2 net-next 0/8] DSA changes for multiple CPU ports (part 1) Vladimir Oltean
2022-05-11 9:50 ` [PATCH v2 net-next 1/8] net: dsa: felix: program host FDB entries towards PGID_CPU for tag_8021q too Vladimir Oltean
2022-05-11 10:57 ` Vladimir Oltean
2022-05-11 9:50 ` [PATCH v2 net-next 2/8] net: dsa: felix: bring the NPI port indirection for host MDBs to surface Vladimir Oltean
2022-05-11 9:50 ` [PATCH v2 net-next 3/8] net: dsa: felix: bring the NPI port indirection for host flooding " Vladimir Oltean
2022-05-11 9:50 ` [PATCH v2 net-next 4/8] net: dsa: introduce the dsa_cpu_ports() helper Vladimir Oltean
2022-05-11 9:50 ` [PATCH v2 net-next 5/8] net: dsa: felix: manage host flooding using a specific driver callback Vladimir Oltean
2022-05-11 9:50 ` [PATCH v2 net-next 6/8] net: dsa: remove port argument from ->change_tag_protocol() Vladimir Oltean
2022-05-11 9:50 ` [PATCH v2 net-next 7/8] net: dsa: felix: dynamically determine tag_8021q CPU port for traps Vladimir Oltean
2022-05-11 9:50 ` [PATCH v2 net-next 8/8] net: dsa: felix: reimplement tagging protocol change with function pointers Vladimir Oltean
2022-05-12 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=165239941497.20203.10953892440196302945.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alsi@bang-olufsen.dk \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=claudiu.manoil@nxp.com \
--cc=colin.foster@in-advantage.com \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kabel@kernel.org \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=luizluca@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.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