From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, vivien.didelot@gmail.com,
f.fainelli@gmail.com, olteanv@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
george.mccollister@gmail.com, kurt@linutronix.de,
matthias.bgg@gmail.com, woojung.huh@microchip.com,
UNGLinuxDriver@microchip.com, linus.walleij@linaro.org,
alsi@bang-olufsen.dk, clement.leger@bootlin.com,
arinc.unal@arinc9.com, Landen.Chao@mediatek.com,
dqfext@gmail.com, sean.wang@mediatek.com, marex@denx.de,
john@phrozen.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] Remove label = "cpu" from DSA dt-bindings
Date: Tue, 20 Sep 2022 01:10:20 +0000 [thread overview]
Message-ID: <166363622085.23429.2523783707495550803.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220912175058.280386-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 12 Sep 2022 20:50:55 +0300 you wrote:
> As explained in more detail in patch 1/3, label = "cpu" is not part of
> DSA's device tree bindings, yet we have some checks in the dt-schema for
> mt7530 which are written as if it was.
>
> Reformulate those checks, and remove all occurrences of this seemingly
> used, but actually unused, property from the binding examples.
>
> [...]
Here is the summary with links:
- [net-next,1/3] dt-bindings: net: dsa: mt7530: replace label = "cpu" with proper checks
https://git.kernel.org/netdev/net-next/c/3f301a280078
- [net-next,2/3] dt-bindings: net: dsa: mt7530: stop requiring phy-mode on CPU ports
https://git.kernel.org/netdev/net-next/c/cdd3e486d705
- [net-next,3/3] dt-bindings: net: dsa: remove label = "cpu" from examples
https://git.kernel.org/netdev/net-next/c/9cc115d8d6f7
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-09-20 1:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 17:50 [PATCH net-next 0/3] Remove label = "cpu" from DSA dt-bindings Vladimir Oltean
2022-09-12 17:50 ` [PATCH net-next 1/3] dt-bindings: net: dsa: mt7530: replace label = "cpu" with proper checks Vladimir Oltean
2022-09-12 17:59 ` Florian Fainelli
2022-09-13 8:19 ` Arınç ÜNAL
2022-09-13 15:51 ` Rob Herring
2022-09-13 15:55 ` Arınç ÜNAL
2022-09-13 16:26 ` Vladimir Oltean
2022-09-12 17:50 ` [PATCH net-next 2/3] dt-bindings: net: dsa: mt7530: stop requiring phy-mode on CPU ports Vladimir Oltean
2022-09-12 18:07 ` Florian Fainelli
2022-09-13 8:19 ` Arınç ÜNAL
2022-09-13 15:51 ` Rob Herring
2022-09-12 17:50 ` [PATCH net-next 3/3] dt-bindings: net: dsa: remove label = "cpu" from examples Vladimir Oltean
2022-09-12 18:12 ` Florian Fainelli
2022-09-13 8:20 ` Arınç ÜNAL
2022-09-13 13:31 ` Vladimir Oltean
2022-09-13 14:14 ` Arınç ÜNAL
2022-09-13 14:32 ` Vladimir Oltean
2022-09-13 15:54 ` Rob Herring
2022-09-13 15:54 ` Rob Herring
2022-09-20 1: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=166363622085.23429.2523783707495550803.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Landen.Chao@mediatek.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alsi@bang-olufsen.dk \
--cc=andrew@lunn.ch \
--cc=arinc.unal@arinc9.com \
--cc=clement.leger@bootlin.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dqfext@gmail.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=george.mccollister@gmail.com \
--cc=john@phrozen.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marex@denx.de \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.com \
--cc=woojung.huh@microchip.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).