From: Andrew Lunn <andrew@lunn.ch>
To: "Michał Grzelak" <mig@semihalf.com>
Cc: linux-kernel@vger.kernel.org, sebastian.hesselbarth@gmail.com,
gregory.clement@bootlin.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
mw@semihalf.com, upstream@semihalf.com, mchl.grzlk@gmail.com
Subject: Re: [PATCH v3] ARM: dts: dove.dtsi: Move ethphy to fix schema error
Date: Fri, 30 Dec 2022 17:00:01 +0100 [thread overview]
Message-ID: <Y68LASVPztAWYVfX@lunn.ch> (raw)
In-Reply-To: <20221229180155.99303-1-mig@semihalf.com>
On Thu, Dec 29, 2022 at 07:01:55PM +0100, Michał Grzelak wrote:
> Running 'make dtbs_check' with schema in net/marvell,orion-mdio.yaml
> gives following warnings:
> mdio-bus@72004: Unevaluated properties are not allowed
> ('ethernet-phy' was unexpected)
> arch/arm/boot/dts/dove-cubox.dtb
> arch/arm/boot/dts/dove-cubox-es.dtb
> arch/arm/boot/dts/dove-d2plug.dtb
> arch/arm/boot/dts/dove-d2plug.dtb
> arch/arm/boot/dts/dove-dove-db.dtb
> arch/arm/boot/dts/dove-d3plug.dtb
> arch/arm/boot/dts/dove-sbc-a510.dtb
> As every subnode of mdio is expected to have an @X, ethernet-phy subnode
> in dove.dtsi doesn't have one. Fix these errors by moving ethernet-phy
> into relevant .dts files with correct @<reg address>.
>
> Signed-off-by: Michał Grzelak <mig@semihalf.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-12-30 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 18:01 [PATCH v3] ARM: dts: dove.dtsi: Move ethphy to fix schema error Michał Grzelak
2022-12-30 16:00 ` Andrew Lunn [this message]
2023-01-31 14:39 ` Gregory CLEMENT
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=Y68LASVPztAWYVfX@lunn.ch \
--to=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchl.grzlk@gmail.com \
--cc=mig@semihalf.com \
--cc=mw@semihalf.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=upstream@semihalf.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).