From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Cc: Saravana Kannan <saravanak@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 00/10] dtc: dt-check-style: Improvements for false positives
Date: Wed, 26 Aug 2026 10:20:19 -0500 [thread overview]
Message-ID: <20260826152019.GA1769013-robh@kernel.org> (raw)
In-Reply-To: <20260826-n-dts-style-checker-continued-v6-0-f270b1e81f8e@oss.qualcomm.com>
On Wed, Aug 26, 2026 at 01:15:52PM +0200, Krzysztof Kozlowski wrote:
> This might be a frequent posting, because Sashiko finds a lot of border
> cases. It turns out parsing text is not that easy (surprise!).
>
> Changes in v6:
> - Handle white-space differences in overlays '&{/} {' part
> - Bring back strip() from _strip_strings_and_comments() rework
> - Minor commit msg improvements
> - Link to v5: https://patch.msgid.link/20260826-n-dts-style-checker-continued-v5-0-fdd16ca6e771@oss.qualcomm.com
>
> Changes in v5:
> - Patch #3: Trailing whitespace or comments break multi-line property alignment validation
> - Patch #9: The regular expression `r'(\s\s+|\t){'` uses an unescaped `{`
> The redundant whitespace checks do not validate continuation lines of multi-line properties
> - More tests for each of cases brought by Sashiko
> - Link to v4: https://patch.msgid.link/20260826-n-dts-style-checker-continued-v4-0-022e60091965@oss.qualcomm.com
>
> Changes in v4:
> - First two patches merged
> - Squashed previous #3 into next one (#4... but now it is patch #1),
> because: detection of root is still needed for DTS/DTSO with code:
> &soc {
> children ...
> };
> where comparing the c.parent.node_name to None or / would give false
> results of being child of root node.
> Fix regex pattern for "/{" case.
> - Fix comments from Sashiko (rebasing issue, help msg, align continued
> values based on previous one ending with ',', do not report whitespace
> issues for comments)
> - More test fixtures
> - New patches:
> dtc: dt-check-style: Replace Test User email with Rob Herring
> dtc: dt-check-style: Call _strip_strings_and_comments() only once
> - Link to v3: https://patch.msgid.link/20260803-n-dts-style-checker-continued-v3-0-6c9776928cea@oss.qualcomm.com
>
> Changes in v3:
> - Responded to Sashiko and implemented its comments
> - Properly handle root node with more than one space "/ {"
> - Add more unit tests for DTSO whether properties and nodes are properly
> detected as top-level
> - Link to v2: https://patch.msgid.link/20260802-n-dts-style-checker-continued-v2-0-6c5dbd1ccfe4@oss.qualcomm.com
>
> Changes in v2:
> - Trailing slash to maintainers path
> - New patches:
> - Patch #9: dtc: dt-check-style: Add test for trailing white-space in DTS
> - Patch #10: dtc: dt-check-style: Add warning for redundant white-spaces
> - Several fixes based on Sashiko's report (I responded to these on the
> lists)
> - _walk_bodies(): Fix setting up proper parent to each node after
> exiting node parsing. This wasn't working correctly.
> - check_child_name_order(): Properly sort top-level nodes by names,
> even if it comes with unit address like memory@1000
> - Add rest of property_bucket sorting for top-level properties,
> even though no properties are expected there, except few vendor
> ones
> - check_continuation_alignment(): Improve error msg for
> continuned-lines alignment warnings
>
> - Link to v1: https://patch.msgid.link/20260726-n-dts-style-checker-continued-v1-0-b05b8f897670@oss.qualcomm.com
>
> Few improvements and proper handling of top-level node (name, not unit
> address sorting) and property (model before compatible) sorting.
>
> Best regards,
> Krzysztof
>
> ---
> Krzysztof Kozlowski (10):
> dtc: dt-check-style: Handle sorting of top-level nodes and properties
> dtc: dt-check-style: Drop stray backslash before quote for continuation-alignment
> dtc: dt-check-style: Fix alignment of values in continued property lines
> dtc: dt-check-style: Consistently call 'kind' as 'file_type'
> dtc: dt-check-style: Introduce 'stricter' mode
> dtc: dt-check-style: Replace Test User email with Rob Herring
> dtc: dt-check-style: Call _strip_strings_and_comments() only once
> dtc: dt-check-style: Add test for trailing white-space in DTS
> dtc: dt-check-style: Add warning for redundant white-spaces
> MAINTAINERS: dt-bindings: Include dt-check-style in DT binding entry
The remaining sashiko issues look unlikely to me, so I applied the
series.
Rob
prev parent reply other threads:[~2026-08-26 15:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 11:15 [PATCH v6 00/10] dtc: dt-check-style: Improvements for false positives Krzysztof Kozlowski
2026-08-26 11:15 ` [PATCH v6 01/10] dtc: dt-check-style: Handle sorting of top-level nodes and properties Krzysztof Kozlowski
2026-08-26 11:26 ` sashiko-bot
2026-08-26 11:15 ` [PATCH v6 02/10] dtc: dt-check-style: Drop stray backslash before quote for continuation-alignment Krzysztof Kozlowski
2026-08-26 11:15 ` [PATCH v6 03/10] dtc: dt-check-style: Fix alignment of values in continued property lines Krzysztof Kozlowski
2026-08-26 11:23 ` sashiko-bot
2026-08-26 11:15 ` [PATCH v6 04/10] dtc: dt-check-style: Consistently call 'kind' as 'file_type' Krzysztof Kozlowski
2026-08-26 11:15 ` [PATCH v6 05/10] dtc: dt-check-style: Introduce 'stricter' mode Krzysztof Kozlowski
2026-08-26 11:15 ` [PATCH v6 06/10] dtc: dt-check-style: Replace Test User email with Rob Herring Krzysztof Kozlowski
2026-08-26 11:15 ` [PATCH v6 07/10] dtc: dt-check-style: Call _strip_strings_and_comments() only once Krzysztof Kozlowski
2026-08-26 11:16 ` [PATCH v6 08/10] dtc: dt-check-style: Add test for trailing white-space in DTS Krzysztof Kozlowski
2026-08-26 11:16 ` [PATCH v6 09/10] dtc: dt-check-style: Add warning for redundant white-spaces Krzysztof Kozlowski
2026-08-26 11:16 ` [PATCH v6 10/10] MAINTAINERS: dt-bindings: Include dt-check-style in DT binding entry Krzysztof Kozlowski
2026-08-26 15:20 ` Rob Herring [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=20260826152019.GA1769013-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=saravanak@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 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.