From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Zev Weiss <zev@bewilderbeest.net>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
openbmc@lists.ozlabs.org
Subject: Re: [PATCH 2/2] ARM: dts: aspeed: Add ASRock E3C256D4I BMC
Date: Wed, 15 Nov 2023 13:13:56 +0100 [thread overview]
Message-ID: <6bb81878-2b68-4721-86c0-5f6eaec59434@linaro.org> (raw)
In-Reply-To: <b06b2b9e-8185-41e8-89b5-e6bc8d09d948@hatter.bewilderbeest.net>
On 14/11/2023 23:21, Zev Weiss wrote:
>> It does not look like you tested the DTS against bindings. Please run
>> `make dtbs_check W=1` (see
>> Documentation/devicetree/bindings/writing-schema.rst or
>> https://www.linaro.org/blog/tips-and-tricks-for-validating-devicetree-sources-with-the-devicetree-schema/
>> for instructions).
>>
>
> Au contraire -- I did, and it exited 0 with no output, which I
> interpreted as a clean pass. Are there particular shortcomings beside
> what you've already pointed out that you would have expected it to flag?
Then paste entire command result here, including the command you used.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-11-15 12:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 11:27 [PATCH 0/2] " Zev Weiss
2023-11-14 11:27 ` [PATCH 1/2] dt-bindings: arm: aspeed: document ASRock E3C256D4I Zev Weiss
2023-11-14 20:34 ` Krzysztof Kozlowski
2023-11-14 11:27 ` [PATCH 2/2] ARM: dts: aspeed: Add ASRock E3C256D4I BMC Zev Weiss
2023-11-14 20:35 ` Krzysztof Kozlowski
2023-11-14 22:21 ` Zev Weiss
2023-11-15 12:13 ` Krzysztof Kozlowski [this message]
2023-11-14 22:37 ` Zev Weiss
2023-11-14 22:55 ` Zev Weiss
2023-11-15 12:13 ` Krzysztof Kozlowski
2023-11-16 2:39 ` Zev Weiss
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=6bb81878-2b68-4721-86c0-5f6eaec59434@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=krzysztof.kozlowski+dt@linaro.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=zev@bewilderbeest.net \
/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
all inboxes | Powered by JetHome®