From: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
To: sashiko-reviews@lists.linux.dev
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 7/7] dtc: dt-check-style: Relax property ordering rules (drop alphabetical)
Date: Wed, 16 Sep 2026 07:50:40 +0200 [thread overview]
Message-ID: <84ab621c-61d2-4da6-884b-05118e093d88@oss.qualcomm.com> (raw)
In-Reply-To: <20260915173834.29EF31F000FF@smtp.kernel.org>
On 15/09/2026 19:38, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] scripts/dtc: missing pairing rule for #size-cells in dt-check-style
Not yet implemented.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-09-16 5:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 17:03 [PATCH v4 0/7] dtc: dt-check-style: Improvements for handling continued lines Krzysztof Kozlowski
2026-09-15 17:03 ` [PATCH v4 1/7] dtc: dt-check-style: Handle continued lines in check_hex_case() Krzysztof Kozlowski
2026-09-15 17:03 ` [PATCH v4 2/7] dtc: dt-check-style: Handle continued lines in check_line_length() Krzysztof Kozlowski
2026-09-15 17:03 ` [PATCH v4 3/7] dtc: dt-check-style: Handle continued lines in check_trailing_whitespace() Krzysztof Kozlowski
2026-09-15 17:03 ` [PATCH v4 4/7] dtc: dt-check-style: Unduplicate checks in check_mixed_indent_chars() Krzysztof Kozlowski
2026-09-15 17:03 ` [PATCH v4 5/7] dtc: dt-check-style: Right strip whitespaces, leftovers before comments Krzysztof Kozlowski
2026-09-15 17:03 ` [PATCH v4 6/7] dtc: dt-check-style: Properly detect comments in multi-line properties Krzysztof Kozlowski
2026-09-15 17:03 ` [PATCH v4 7/7] dtc: dt-check-style: Relax property ordering rules (drop alphabetical) Krzysztof Kozlowski
2026-09-15 17:38 ` sashiko-bot
2026-09-16 5:50 ` Krzysztof Kozlowski [this message]
2026-09-16 20:20 ` [PATCH v4 0/7] dtc: dt-check-style: Improvements for handling continued lines Rob Herring
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=84ab621c-61d2-4da6-884b-05118e093d88@oss.qualcomm.com \
--to=krzysztof.kozlowski@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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