From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ricardo Ribalda <ribalda@chromium.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: 6.16rc1 dts-bindings check fails
Date: Wed, 11 Jun 2025 08:41:00 +0200 [thread overview]
Message-ID: <a2efd2e3-bab8-43ba-a236-aa5052bc35c7@kernel.org> (raw)
In-Reply-To: <CANiDSCvB5yytOgvk1QC812x4zOBn5Z4_C5wqUnV+2hSQXKM54g@mail.gmail.com>
On 10/06/2025 18:11, Ricardo Ribalda wrote:
> Hi
>
> Media-CI is reporting some dts binding errors:
Every builder of linux-next sees this, it's not specific to media.
>
> /builds/linux-media/users/ribalda/Documentation/devicetree/bindings/crypto/marvell,orion-crypto.yaml:
> properties:reg-names:items:1: 'deprecated' is not one of ['const',
> 'description', 'enum', 'not', 'pattern']
> from schema $id: http://devicetree.org/meta-schemas/string-array.yaml#
> /builds/linux-media/users/ribalda/Documentation/devicetree/bindings/pci/marvell,armada8k-pcie.example.dtb:
> pcie@f2600000: interrupts: [[0], [32], [4]] is too long
> from schema $id: http://devicetree.org/schemas/pci/marvell,armada8k-pcie.yaml#
>
> When I test your for-next tree I have the same issue:
> https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git/log/Documentation/devicetree/bindings/crypto?h=for-next
>
> They do not affect media drivers so right now I am just ignoring them,
> but I wanted to know if they are under your radar.
>
You need to update your dtschema.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-06-11 6:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 16:11 6.16rc1 dts-bindings check fails Ricardo Ribalda
2025-06-11 6:41 ` Krzysztof Kozlowski [this message]
2025-06-11 7:06 ` Ricardo Ribalda
2025-06-11 7:11 ` Krzysztof Kozlowski
2025-06-11 7:24 ` Ricardo Ribalda
2025-06-13 0:47 ` Rob Herring
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=a2efd2e3-bab8-43ba-a236-aa5052bc35c7@kernel.org \
--to=krzk@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=ribalda@chromium.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