From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Rajaganesh Rathinasabapathi <Rajaganesh.Rathinasabapathi@amd.com>
Cc: "Rob Herring (Arm)" <robh@kernel.org>,
joel@jms.id.au, robh+dt@kernel.org, openbmc@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, jothayot@amd.com,
linux-aspeed@lists.ozlabs.org, krzk+dt@kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 1/2] dt-bindings: arm: aspeed: Add AMD Onyx BMC compatible
Date: Fri, 21 Mar 2025 11:09:29 +1030 [thread overview]
Message-ID: <158f6e8e6c41250d6b88c5f2b5dc6df5d728222b.camel@codeconstruct.com.au> (raw)
In-Reply-To: <174233663954.4094319.18412685456723022993.robh@kernel.org>
On Tue, 2025-03-18 at 17:26 -0500, Rob Herring (Arm) wrote:
>
> On Tue, 18 Mar 2025 12:47:29 -0500, Rajaganesh Rathinasabapathi wrote:
> > Document new AMD Onyx BMC board compatibles
> >
> > Signed-off-by: Rajaganesh Rathinasabapathi <Rajaganesh.Rathinasabapathi@amd.com>
> > ---
> > Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml | 1 +
> > 1 file changed, 1 insertion(+)
> >
>
>
> My bot found new DTB warnings on the .dts files added or changed in this
> series.
>
> Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
> are fixed by another series. Ultimately, it is up to the platform
> maintainer whether these warnings are acceptable or not. No need to reply
> unless the platform maintainer has comments.
>
> If you already ran DT checks and didn't see these error(s), then
> make sure dt-schema is up to date:
>
> pip3 install dtschema --upgrade
>
>
> New warnings running 'make CHECK_DTBS=y for arch/arm/boot/dts/aspeed/' for 20250318174730.1921983-1-Rajaganesh.Rathinasabapathi@amd.com:
>
...
>
> arch/arm/boot/dts/aspeed/aspeed-bmc-amd-onyx.dtb: mbeeprom@50: $nodename:0: 'mbeeprom@50' does not match '^eeprom@[0-9a-f]{1,2}$'
> from schema $id: http://devicetree.org/schemas/eeprom/at24.yaml#
> arch/arm/boot/dts/aspeed/aspeed-bmc-amd-onyx.dtb: mbeeprom@50: Unevaluated properties are not allowed ('$nodename' was unexpected)
> from schema $id: http://devicetree.org/schemas/eeprom/at24.yaml#
Rajaganesh: Please fix these warnings before you send v5.
Andrew
prev parent reply other threads:[~2025-03-21 0:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 17:47 [PATCH v4 1/2] dt-bindings: arm: aspeed: Add AMD Onyx BMC compatible Rajaganesh Rathinasabapathi
2025-03-18 17:47 ` [PATCH v4 2/2] ARM: dts: aspeed: Add Initial device tree for AMD Onyx Platform Rajaganesh Rathinasabapathi
2025-03-18 18:14 ` Krzysztof Kozlowski
2025-03-19 16:41 ` Rajaganesh Rathinasabapathi
2025-03-19 19:23 ` Krzysztof Kozlowski
2025-03-18 18:33 ` Andrew Lunn
2025-03-19 16:47 ` Rajaganesh Rathinasabapathi
2025-03-18 18:10 ` [PATCH v4 1/2] dt-bindings: arm: aspeed: Add AMD Onyx BMC compatible Krzysztof Kozlowski
2025-03-18 22:26 ` Rob Herring (Arm)
2025-03-21 0:39 ` Andrew Jeffery [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=158f6e8e6c41250d6b88c5f2b5dc6df5d728222b.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=Rajaganesh.Rathinasabapathi@amd.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=jothayot@amd.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
/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