From: Chris Packham <chris.packham@alliedtelesis.co.nz>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, andrew@lunn.ch,
gregory.clement@bootlin.com, sebastian.hesselbarth@gmail.com,
kabel@kernel.org
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: [PATCH 0/2] armada-3720-turris-mox and orion-mdio
Date: Tue, 17 May 2022 10:47:59 +1200 [thread overview]
Message-ID: <20220516224801.1656752-1-chris.packham@alliedtelesis.co.nz> (raw)
This is a follow up to the change that converted the orion-mdio dt-binding from
txt to DT schema format. At the time I thought the binding needed
'unevaluatedProperties: false' because the core mdio.yaml binding didn't handle
the DSA switches. In reality it was simply the invalid reg property causing the
downstream nodes to be unevaluated. Fixing the reg nodes means we can set
'unevaluatedProperties: true'
Marek,
I don't know if you had a change for the reg properties in flight. I didn't see
anything on lore/lkml so sorry if this crosses with something you've done.
Chris Packham (2):
arm64: dts: armada-3720-turris-mox: Correct reg property for mdio
devices
dt-bindings: net: marvell,orion-mdio: Set unevaluatedProperties to
false
.../devicetree/bindings/net/marvell,orion-mdio.yaml | 2 +-
.../boot/dts/marvell/armada-3720-turris-mox.dts | 12 ++++++------
2 files changed, 7 insertions(+), 7 deletions(-)
--
2.36.1
next reply other threads:[~2022-05-16 22:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 22:47 Chris Packham [this message]
2022-05-16 22:48 ` [PATCH 1/2] arm64: dts: armada-3720-turris-mox: Correct reg property for mdio devices Chris Packham
2022-05-17 16:21 ` Marek Behún
2022-05-16 22:48 ` [PATCH 2/2] dt-bindings: net: marvell,orion-mdio: Set unevaluatedProperties to false Chris Packham
2022-05-17 15:11 ` Rob Herring
2022-05-18 12:10 ` [PATCH 0/2] armada-3720-turris-mox and orion-mdio patchwork-bot+netdevbpf
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=20220516224801.1656752-1-chris.packham@alliedtelesis.co.nz \
--to=chris.packham@alliedtelesis.co.nz \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=gregory.clement@bootlin.com \
--cc=kabel@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.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).