From: sashiko-bot@kernel.org
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@oss.qualcomm.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v3 10/11] dtc: dt-check-style: Add warning for redundant white-spaces
Date: Mon, 03 Aug 2026 09:13:31 +0000 [thread overview]
Message-ID: <20260803091332.53D661F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260803-n-dts-style-checker-continued-v3-10-6c9776928cea@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] False positives in dt-check-style whitespace checks due to unstripped strings and inline comments.
--
--- Patch [10]: [PATCH v3 10/11] dtc: dt-check-style: Add warning for redundant white-spaces ---
commit f5a3cbd31bda433ce990bca1b2244f3a3da27d87
Author: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
dtc: dt-check-style: Add warning for redundant white-spaces
This commit adds a warning in dt-check-style to catch excessive spaces or
tabs around '=', before '{', and before ';'. The checking is split between
relaxed and strict modes to accommodate existing in-tree usage.
> diff --git a/scripts/dtc/dt-check-style b/scripts/dtc/dt-check-style
> index 1430c675bd951..aa2072957a1a0 100755
> --- a/scripts/dtc/dt-check-style
> +++ b/scripts/dtc/dt-check-style
> @@ -348,6 +348,36 @@ def check_trailing_whitespace(ctx):
> yield (dl.lineno, 'trailing whitespace')
>
>
> +def check_redundant_whitespace(ctx):
> + """No whitespace between brackets or other code elements.
> + See also check_value_whitespace() for more checks."""
> + for dl in ctx.lines:
> + if dl.linetype in (LineType.COMMENT, LineType.COMMENT_BODY,
> + LineType.COMMENT_END, LineType.COMMENT_START,
> + LineType.PREPROCESSOR):
> + continue
> + if re.search(r'(\s\s+|\t){', dl.raw):
> + yield (dl.lineno, 'extra whitespace before {')
> + if re.search(r':(\s\s+|\t)', dl.raw):
> + yield (dl.lineno, 'extra whitespace after :')
> + if re.search(r'\s+;', dl.raw):
[Severity: Medium]
Does using dl.raw directly here cause false positives for inline comments or
string literals?
For example, if a line has bootargs = "console=ttyS0 rdinit=/init"; or
reg = <1>; /* my comment ; */, since re.search evaluates dl.raw directly,
it looks like it will match the whitespace inside the string or the inline
comment.
Would it be safer to strip comments or strings via
_strip_strings_and_comments(dl.raw) before evaluating the regular expressions?
> + yield (dl.lineno, 'extra whitespace before ;')
> +
> +
> +def check_redundant_whitespace_strict(ctx):
> + """No whitespace between brackets or other code elements.
> + See also check_value_whitespace() for more checks."""
> + for dl in ctx.lines:
> + if dl.linetype in (LineType.COMMENT, LineType.COMMENT_BODY,
> + LineType.COMMENT_END, LineType.COMMENT_START,
> + LineType.PREPROCESSOR):
> + continue
> + if re.search(r'(\s\s+|\t)=', dl.raw):
> + yield (dl.lineno, 'extra whitespace before =')
> + if re.search(r'=(\s\s+|\t)', dl.raw):
[Severity: Medium]
Similarly, will this strict check also trigger false positives on strings
that intentionally contain multiple spaces, such as
compatible = "vendor,device v2";, because dl.raw retains the unstripped
string content?
> + yield (dl.lineno, 'extra whitespace after =')
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260803-n-dts-style-checker-continued-v3-0-6c9776928cea@oss.qualcomm.com?part=10
next prev parent reply other threads:[~2026-08-03 9:13 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
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 [this message]
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=20260803091332.53D661F000E9@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.