From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v4 1/2] dt-bindings: arm: aspeed: document AMD DaytonaX
Date: Thu, 22 Sep 2022 08:47:14 +0200 [thread overview]
Message-ID: <035f5834-6fb7-95ba-1569-6dbf8eface49@linaro.org> (raw)
In-Reply-To: <20220922063514.f6euqlw35jrkpee4@krzk-bin>
On 22/09/2022 08:35, Krzysztof Kozlowski wrote:
> On Thu, 22 Sep 2022 00:09:46 +0300, Konstantin Aladyshev wrote:
>> Document AMD DaytonaX board compatible.
>>
>> Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
>> ---
>> Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml | 1 +
>> 1 file changed, 1 insertion(+)
>>
>
> Running 'make dtbs_check' with the schema in this patch gives the
> following warnings. Consider if they are expected or the schema is
> incorrect. These may not be new warnings.
>
> Note that it is not yet a requirement to have 0 warnings for dtbs_check.
> This will change in the future.
>
> Full log is available here: https://patchwork.ozlabs.org/patch/1680833
>
>
> /: compatible: 'oneOf' conditional failed, one must be fixed:
> arch/arm/boot/dts/aspeed-bmc-qcom-dc-scm-v1.dtb
Ignore, this is not related.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-09-22 6:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 16:54 [PATCH v3] ARM: dts: aspeed: Add AMD DaytonaX BMC Konstantin Aladyshev
2022-09-21 7:00 ` Krzysztof Kozlowski
2022-09-21 7:07 ` Krzysztof Kozlowski
2022-09-21 21:09 ` [PATCH v4 0/2] " Konstantin Aladyshev
2022-09-21 21:09 ` [PATCH v4 1/2] dt-bindings: arm: aspeed: document AMD DaytonaX Konstantin Aladyshev
2022-09-22 6:35 ` Krzysztof Kozlowski
2022-09-22 6:47 ` Krzysztof Kozlowski [this message]
2022-09-22 6:46 ` Krzysztof Kozlowski
2022-09-21 21:09 ` [PATCH v4 2/2] ARM: dts: aspeed: Add AMD DaytonaX BMC Konstantin Aladyshev
2022-09-21 21:15 ` Konstantin Aladyshev
2022-09-22 6:52 ` Krzysztof Kozlowski
2022-09-22 6:52 ` Krzysztof Kozlowski
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=035f5834-6fb7-95ba-1569-6dbf8eface49@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=linux-aspeed@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).