From: sashiko-bot@kernel.org
To: "Shaunak Datar" <shaunakkdatar@gmail.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH] dt-bindings: thermal: kirkwood-thermal: Convert to DT Schema
Date: Thu, 12 Nov 2026 07:38:17 +0000 [thread overview]
Message-ID: <sashiko-outbox-210620@kernel.org> (raw)
In-Reply-To: <20261112072925.22075-1-shaunakkdatar@gmail.com>
Thank you for your contribution! Sashiko AI review found 3 potential
issues to consider:
- [Medium] dt-bindings: thermal: scalar maintainers string breaks schema
validation
- [Low] dt-bindings: thermal: missing newline at end of
kirkwood-thermal.yaml
- [Low] dt-bindings: thermal: kirkwood-thermal.yaml filename omits
vendor prefix
--
commit 70c9f13751a18e94c7372bae17a84a1ba365709a
Author: Shaunak Datar <shaunakkdatar@gmail.com>
dt-bindings: thermal: kirkwood-thermal: Convert to DT Schema
This commit converts the Marvell Kirkwood thermal sensor device tree
binding from plain text to a YAML schema.
> diff --git a/Documentation/devicetree/bindings/thermal/kirkwood-thermal.yaml b/Documentation/devicetree/bindings/thermal/kirkwood-thermal.yaml
> new file mode 100644
> index 0000000000000..1f9b97bdd48fa
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/thermal/kirkwood-thermal.yaml
> @@ -0,0 +1,32 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/thermal/kirkwood-thermal.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
[Severity: Low]
Should this file and its $id URI be named marvell,kirkwood-thermal.yaml to
match the compatible string and the vendor,device.yaml convention used by
sibling Marvell thermal bindings?
> +
> +title: Kirkwood Thermal
> +
> +maintainers: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
[Severity: Medium]
Does defining maintainers as a scalar string instead of a YAML list cause
make dt_binding_check to fail? core.yaml requires maintainers to be an
array, so dt-doc-validate rejects this schema and dtbs_check skips it.
[ ... ]
> +examples:
> + - |
> + thermal@10078 {
> + compatible = "marvell,kirkwood-thermal";
> + reg = <0x10078 0x4>;
> + };
> \ No newline at end of file
[Severity: Low]
Does the missing newline at the end of the file cause yamllint to fail
during make dt_binding_check?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261112072925.22075-1-shaunakkdatar@gmail.com?part=1
prev parent reply other threads:[~2026-11-12 7:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 7:29 [PATCH] dt-bindings: thermal: kirkwood-thermal: Convert to DT Schema Shaunak Datar
2026-11-12 7:38 ` sashiko-bot [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=sashiko-outbox-210620@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=shaunakkdatar@gmail.com \
/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