From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
devicetree@vger.kernel.org,
Andrew Jeffery <andrew@codeconstruct.com.au>,
Joel Stanley <joel@jms.id.au>,
linux-arm-kernel@lists.infradead.org,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, linux-aspeed@lists.ozlabs.org
Subject: Re: [PATCH v2 1/5] ARM: dts: aspeed: greatlakes: correct Mellanox multi-host property
Date: Tue, 9 Apr 2024 16:00:47 +0200 [thread overview]
Message-ID: <5e80dc7b-e848-46d5-879b-b72c1ac6ba97@linaro.org> (raw)
In-Reply-To: <171266958251.1032405.3082451019333889181.robh@kernel.org>
On 09/04/2024 15:38, Rob Herring wrote:
>
> On Fri, 05 Apr 2024 08:46:20 +0200, Krzysztof Kozlowski wrote:
>> "mlx,multi-host" is using incorrect vendor prefix and is not documented.
>>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>
>> ---
>>
>> Changes in v2:
>> 1. None
>> ---
>> arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-greatlakes.dts | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>
>
> 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 aspeed/aspeed-bmc-ampere-mtmitchell.dtb aspeed/aspeed-bmc-facebook-greatlakes.dtb aspeed/aspeed-bmc-facebook-harma.dtb aspeed/aspeed-bmc-facebook-yosemite4.dtb aspeed/aspeed-bmc-facebook-yosemitev2.dtb' for 20240405064624.18997-1-krzysztof.kozlowski@linaro.org:
>
> arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-harma.dtb: ftgmac@1e690000: Unevaluated properties are not allowed ('#address-cells', '#size-cells', 'mellanox,multi-host' were unexpected)
> from schema $id: http://devicetree.org/schemas/net/faraday,ftgmac100.yaml#
>
Just FYI
These warnings are expected and not a result of my patches.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-04-09 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 6:46 [PATCH v2 1/5] ARM: dts: aspeed: greatlakes: correct Mellanox multi-host property Krzysztof Kozlowski
2024-04-05 6:46 ` [PATCH v2 2/5] ARM: dts: aspeed: yosemite4: " Krzysztof Kozlowski
2024-04-05 6:46 ` [PATCH v2 3/5] ARM: dts: aspeed: yosemitev2: " Krzysztof Kozlowski
2024-04-05 6:46 ` [PATCH v2 4/5] ARM: dts: aspeed: harma: " Krzysztof Kozlowski
2024-04-05 6:46 ` [PATCH v2 5/5] ARM: dts: aspeed: drop unused ref_voltage ADC property Krzysztof Kozlowski
2024-04-09 0:24 ` [PATCH v2 1/5] ARM: dts: aspeed: greatlakes: correct Mellanox multi-host property Andrew Jeffery
2024-04-09 13:38 ` Rob Herring
2024-04-09 14:00 ` Krzysztof Kozlowski [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=5e80dc7b-e848-46d5-879b-b72c1ac6ba97@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--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=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