From: "Rob Herring (Arm)" <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Cc: Saravana Kannan <saravanak@kernel.org>,
devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Test User <test@example.com>, Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 02/11] dtc: dt-check-style: Simplify setting depth of DtsLine
Date: Mon, 3 Aug 2026 17:31:16 -0500 [thread overview]
Message-ID: <178579627576.761030.6701982479196885054.robh@kernel.org> (raw)
In-Reply-To: <20260803-n-dts-style-checker-continued-v3-2-6c9776928cea@oss.qualcomm.com>
On Mon, 03 Aug 2026 11:03:05 +0200, Krzysztof Kozlowski wrote:
> When creating new DtsLine object, pass expected indentation depth as
> constructor, instead of assigning it immediately after, so the code will
> be easier to read and explicit (depth is not supposed to change during
> DtsLine lifetime).
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> ---
> scripts/dtc/dt-check-style | 31 +++++++++++--------------------
> 1 file changed, 11 insertions(+), 20 deletions(-)
>
Applied, thanks!
next prev parent reply other threads:[~2026-08-03 22:31 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) [this message]
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
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=178579627576.761030.6701982479196885054.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 \
--cc=test@example.com \
/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