All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v3 08/11] dtc: dt-check-style: Introduce 'stricter' mode
Date: Mon, 03 Aug 2026 09:16:19 +0000	[thread overview]
Message-ID: <20260803091619.827961F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260803-n-dts-style-checker-continued-v3-8-6c9776928cea@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Top-level nodes with the same name but different unit addresses are no longer validated for correct ordering.
--

--- Patch [8]: [PATCH v3 08/11] dtc: dt-check-style: Introduce 'stricter' mode ---
commit 3fa51567db6be5159b622c7ba7a9c229f630ccc8
Author: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>

dtc: dt-check-style: Introduce 'stricter' mode
    
This commit introduces a 'stricter' mode to the dt-check-style script. It
moves the line-length and unused-labels rules for DTS files from 'strict' to
'stricter' to reduce false positives.

> diff --git a/scripts/dtc/dt-check-style b/scripts/dtc/dt-check-style
> index e3adaad1be633..1430c675bd951 100755
> --- a/scripts/dtc/dt-check-style
> +++ b/scripts/dtc/dt-check-style
> @@ -5,12 +5,14 @@
>  # .dts/.dtsi/.dtso source files. Enforces rules from
>  # Documentation/devicetree/bindings/dts-coding-style.rst.

[ ... ]

[Severity: Medium]
Are top-level nodes with the same name but different unit addresses still
validated for correct ordering?

Looking at check_child_name_order() in scripts/dtc/dt-check-style, top-level
addressed nodes are mapped solely to their node_name, completely discarding
their unit address as a secondary sorting key:

scripts/dtc/dt-check-style:check_child_name_order() {
    ...
    unaddressed.append((_natural_sort_key(c.node_name), c))
    ...
}

Because the strict less-than comparison against identically evaluated name keys
evaluates to False, the script silently ignores out-of-order nodes with the
same name:

scripts/dtc/dt-check-style:check_child_name_order() {
    ...
    for i in range(1, len(unaddressed)):
        if unaddressed[i][0] < unaddressed[i - 1][0]:
    ...
}

Does this allow malformed DTS files with out-of-order top-level nodes of the
same name to bypass validation?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260803-n-dts-style-checker-continued-v3-0-6c9776928cea@oss.qualcomm.com?part=8

  reply	other threads:[~2026-08-03  9:16 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03  9:03 [PATCH v3 00/11] dtc: dt-check-style: Improvements for false positives Krzysztof Kozlowski
2026-08-03  9:03 ` [PATCH v3 01/11] dtc: dt-check-style: Add missing /dts-v1/ to few test cases Krzysztof Kozlowski
2026-08-03 22:30   ` Rob Herring (Arm)
2026-08-03  9:03 ` [PATCH v3 02/11] dtc: dt-check-style: Simplify setting depth of DtsLine Krzysztof Kozlowski
2026-08-03 22:31   ` Rob Herring (Arm)
2026-08-03  9:03 ` [PATCH v3 03/11] dtc: dt-check-style: Handle root node in overlays Krzysztof Kozlowski
2026-08-03  9:18   ` sashiko-bot
2026-08-03  9:03 ` [PATCH v3 04/11] dtc: dt-check-style: Handle sorting of top-level nodes and properties Krzysztof Kozlowski
2026-08-03  9:20   ` sashiko-bot
2026-08-05  7:07     ` Krzysztof Kozlowski
2026-08-03  9:03 ` [PATCH v3 05/11] dtc: dt-check-style: Drop stray backslash before quote for continuation-alignment Krzysztof Kozlowski
2026-08-03  9:09   ` sashiko-bot
2026-08-05  7:09     ` Krzysztof Kozlowski
2026-08-03  9:03 ` [PATCH v3 06/11] dtc: dt-check-style: Fix alignment of values in continued property lines Krzysztof Kozlowski
2026-08-03  9:21   ` sashiko-bot
2026-08-05  7:12     ` Krzysztof Kozlowski
2026-08-03  9:03 ` [PATCH v3 07/11] dtc: dt-check-style: Consistently call 'kind' as 'file_type' Krzysztof Kozlowski
2026-08-03  9:03 ` [PATCH v3 08/11] dtc: dt-check-style: Introduce 'stricter' mode Krzysztof Kozlowski
2026-08-03  9:16   ` sashiko-bot [this message]
2026-08-05  7:06     ` Krzysztof Kozlowski
2026-08-03  9:03 ` [PATCH v3 09/11] dtc: dt-check-style: Add test for trailing white-space in DTS Krzysztof Kozlowski
2026-08-03  9:11   ` sashiko-bot
2026-08-05  7:03     ` Krzysztof Kozlowski
2026-08-03  9:03 ` [PATCH v3 10/11] dtc: dt-check-style: Add warning for redundant white-spaces Krzysztof Kozlowski
2026-08-03  9:13   ` sashiko-bot
2026-08-05  7:12     ` Krzysztof Kozlowski
2026-08-03  9:03 ` [PATCH v3 11/11] MAINTAINERS: dt-bindings: Include dt-check-style in DT binding entry 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=20260803091619.827961F000E9@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.