From: sashiko-bot@kernel.org
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@oss.qualcomm.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 7/7] dtc: dt-check-style: Add more DTS test cases
Date: Wed, 08 Jul 2026 14:58:56 +0000 [thread overview]
Message-ID: <20260708145857.840DC1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260708-dts-style-checker-v4-7-c175e6401150@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Missing semicolons at the end of node definitions in multiple newly added Device Tree Source (DTS) test cases.
--
--- Patch [7]: [PATCH v4 7/7] dtc: dt-check-style: Add more DTS test cases ---
commit 62a01452b76be437a860d7d26f7c0086f5c3e54e
Author: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
dtc: dt-check-style: Add more DTS test cases
Add a few more test cases for valid and incorrect DTS for
dt-check-style.
> diff --git a/scripts/dtc/dt-style-selftest/bad/dts-child-name-order.dts b/scripts/dtc/dt-style-selftest/bad/dts-child-name-order.dts
> new file mode 100644
> index 0000000000000..dffc81cffbeb5
> --- /dev/null
> +++ b/scripts/dtc/dt-style-selftest/bad/dts-child-name-order.dts
[ ... ]
> + pmu-2 {
> + compatible = "example,pmu";
> +
> + /* Just reference labels to avoid strict warnings */
> + example,foo = <&foo>, <&label_bar>;
> + }
[Severity: Low]
Does this node definition need a trailing semicolon? It looks like it ends
with } instead of };.
> +};
> diff --git a/scripts/dtc/dt-style-selftest/bad/dts-extend-node-child-name-order.dts b/scripts/dtc/dt-style-selftest/bad/dts-extend-node-child-name-order.dts
> new file mode 100644
> index 0000000000000..19fb800e719fb
> --- /dev/null
> +++ b/scripts/dtc/dt-style-selftest/bad/dts-extend-node-child-name-order.dts
[ ... ]
> + pmu {
> + compatible = "example,pmu";
> +
> + /* Just reference labels to avoid strict warnings */
> + example,foo = <&foo>, <&label_bar>;
> + }
[Severity: Low]
Is a trailing semicolon missing from the pmu node definition?
> +};
[ ... ]
> diff --git a/scripts/dtc/dt-style-selftest/bad/dts-extend-node-digit-node-order.dts b/scripts/dtc/dt-style-selftest/bad/dts-extend-node-digit-node-order.dts
> new file mode 100644
> index 0000000000000..66547a1cd2b5a
> --- /dev/null
> +++ b/scripts/dtc/dt-style-selftest/bad/dts-extend-node-digit-node-order.dts
[ ... ]
> + serial@30000 {
> + compatible = "example,serial";
> + reg = <0x30000 0x1000>;
> + };
> +}
[Severity: Low]
Should this soc override block end with a semicolon?
> diff --git a/scripts/dtc/dt-style-selftest/good/dts-child-name-order.dts b/scripts/dtc/dt-style-selftest/good/dts-child-name-order.dts
> new file mode 100644
> index 0000000000000..b1032885ad486
> --- /dev/null
> +++ b/scripts/dtc/dt-style-selftest/good/dts-child-name-order.dts
[ ... ]
> + pmu-2 {
> + compatible = "example,pmu";
> +
> + /* Just reference labels to avoid strict warnings */
> + example,foo = <&foo>, <&label_bar>;
> + }
[Severity: Low]
Could there be a missing trailing semicolon at the end of this node?
> +};
> diff --git a/scripts/dtc/dt-style-selftest/good/dts-extend-node-child-name-order.dts b/scripts/dtc/dt-style-selftest/good/dts-extend-node-child-name-order.dts
> new file mode 100644
> index 0000000000000..33ce562b72a39
> --- /dev/null
> +++ b/scripts/dtc/dt-style-selftest/good/dts-extend-node-child-name-order.dts
[ ... ]
> + pmu {
> + compatible = "example,pmu";
> +
> + /* Just reference labels to avoid strict warnings */
> + example,foo = <&foo>, <&label_bar>;
> + }
[Severity: Low]
Does this node definition also require a semicolon?
> +};
[ ... ]
> diff --git a/scripts/dtc/dt-style-selftest/good/dts-extend-node-digit-node-order.dts b/scripts/dtc/dt-style-selftest/good/dts-extend-node-digit-node-order.dts
> new file mode 100644
> index 0000000000000..d9f1f533beebd
> --- /dev/null
> +++ b/scripts/dtc/dt-style-selftest/good/dts-extend-node-digit-node-order.dts
[ ... ]
> + serial@30000 {
> + compatible = "example,serial";
> + reg = <0x30000 0x1000>;
> + };
> +}
[Severity: Low]
Should this block end with }; to be a valid Device Tree syntax?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260708-dts-style-checker-v4-0-c175e6401150@oss.qualcomm.com?part=7
prev parent reply other threads:[~2026-07-08 14:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 14:40 [PATCH v4 0/7] dtc: dt-check-style: Improvement after using on DTS Krzysztof Kozlowski
2026-07-08 14:40 ` [PATCH v4 1/7] dtc: dt-check-style: Narrow disallowing of tab in DTS only to YAML Krzysztof Kozlowski
2026-07-08 14:40 ` [PATCH v4 2/7] dtc: dt-check-style: Allow space-aligning indentation in DTS Krzysztof Kozlowski
2026-07-08 14:50 ` sashiko-bot
2026-07-08 14:40 ` [PATCH v4 3/7] dtc: dt-check-style: Rework handling YAML/DTS in rules Krzysztof Kozlowski
2026-07-08 14:40 ` [PATCH v4 4/7] dtc: dt-check-style: Expect first device_type Krzysztof Kozlowski
2026-07-08 14:52 ` sashiko-bot
2026-07-08 14:40 ` [PATCH v4 5/7] dtc: dt-check-style: Handle properly DTC-style includes Krzysztof Kozlowski
2026-07-08 14:40 ` [PATCH v4 6/7] dtc: dt-check-style: Print proper line number of indentation detection place Krzysztof Kozlowski
2026-07-08 14:54 ` sashiko-bot
2026-07-08 14:40 ` [PATCH v4 7/7] dtc: dt-check-style: Add more DTS test cases Krzysztof Kozlowski
2026-07-08 14:58 ` 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=20260708145857.840DC1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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