From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, f.fainelli@gmail.com,
vivien.didelot@gmail.com, andrew@lunn.ch, olteanv@gmail.com,
claudiu.manoil@nxp.com, alexandre.belloni@bootlin.com,
UNGLinuxDriver@microchip.com, colin.foster@in-advantage.com,
roopa@nvidia.com, razor@blackwall.org
Subject: Re: [PATCH v3 net-next 0/9] DSA changes for multiple CPU ports (part 3)
Date: Tue, 23 Aug 2022 10:10:18 +0000 [thread overview]
Message-ID: <166124941811.27612.2369948958047786064.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220819174820.3585002-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 19 Aug 2022 20:48:11 +0300 you wrote:
> Those who have been following part 1:
> https://patchwork.kernel.org/project/netdevbpf/cover/20220511095020.562461-1-vladimir.oltean@nxp.com/
> and part 2:
> https://patchwork.kernel.org/project/netdevbpf/cover/20220521213743.2735445-1-vladimir.oltean@nxp.com/
> will know that 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 3 of that effort.
>
> [...]
Here is the summary with links:
- [v3,net-next,1/9] net: dsa: walk through all changeupper notifier functions
https://git.kernel.org/netdev/net-next/c/4c3f80d22b2e
- [v3,net-next,2/9] net: dsa: don't stop at NOTIFY_OK when calling ds->ops->port_prechangeupper
https://git.kernel.org/netdev/net-next/c/0498277ee17b
- [v3,net-next,3/9] net: bridge: move DSA master bridging restriction to DSA
https://git.kernel.org/netdev/net-next/c/920a33cd7231
- [v3,net-next,4/9] net: dsa: existing DSA masters cannot join upper interfaces
https://git.kernel.org/netdev/net-next/c/4f03dcc6b9a0
- [v3,net-next,5/9] net: dsa: only bring down user ports assigned to a given DSA master
https://git.kernel.org/netdev/net-next/c/7136097e1199
- [v3,net-next,6/9] net: dsa: all DSA masters must be down when changing the tagging protocol
https://git.kernel.org/netdev/net-next/c/f41ec1fd1c20
- [v3,net-next,7/9] net: dsa: use dsa_tree_for_each_cpu_port in dsa_tree_{setup,teardown}_master
https://git.kernel.org/netdev/net-next/c/5dc760d12082
- [v3,net-next,8/9] net: mscc: ocelot: set up tag_8021q CPU ports independent of user port affinity
https://git.kernel.org/netdev/net-next/c/36a0bf443585
- [v3,net-next,9/9] net: mscc: ocelot: adjust forwarding domain for CPU ports in a LAG
https://git.kernel.org/netdev/net-next/c/291ac1517af5
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-08-23 13:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 17:48 [PATCH v3 net-next 0/9] DSA changes for multiple CPU ports (part 3) Vladimir Oltean
2022-08-19 17:48 ` [PATCH v3 net-next 1/9] net: dsa: walk through all changeupper notifier functions Vladimir Oltean
2022-08-19 17:48 ` [PATCH v3 net-next 2/9] net: dsa: don't stop at NOTIFY_OK when calling ds->ops->port_prechangeupper Vladimir Oltean
2022-08-19 17:48 ` [PATCH v3 net-next 3/9] net: bridge: move DSA master bridging restriction to DSA Vladimir Oltean
2022-08-19 17:48 ` [PATCH v3 net-next 4/9] net: dsa: existing DSA masters cannot join upper interfaces Vladimir Oltean
2022-08-19 17:48 ` [PATCH v3 net-next 5/9] net: dsa: only bring down user ports assigned to a given DSA master Vladimir Oltean
2022-08-19 17:48 ` [PATCH v3 net-next 6/9] net: dsa: all DSA masters must be down when changing the tagging protocol Vladimir Oltean
2022-08-19 17:48 ` [PATCH v3 net-next 7/9] net: dsa: use dsa_tree_for_each_cpu_port in dsa_tree_{setup,teardown}_master Vladimir Oltean
2022-08-19 17:48 ` [PATCH v3 net-next 8/9] net: mscc: ocelot: set up tag_8021q CPU ports independent of user port affinity Vladimir Oltean
2022-08-19 17:48 ` [PATCH v3 net-next 9/9] net: mscc: ocelot: adjust forwarding domain for CPU ports in a LAG Vladimir Oltean
2022-08-23 10: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=166124941811.27612.2369948958047786064.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=colin.foster@in-advantage.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.