All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Saravana Kannan <saravanak@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/7] dtc: dt-check-style: Improvements for handling continued lines
Date: Tue, 15 Sep 2026 09:27:42 -0500	[thread overview]
Message-ID: <20260915142742.GA1926857-robh@kernel.org> (raw)
In-Reply-To: <20260909-b4-dts-style-checker-continued-lines-v3-0-474bb324ae53@oss.qualcomm.com>

On Wed, Sep 09, 2026 at 03:10:34PM +0200, Krzysztof Kozlowski wrote:
> Changes in v3:
> - New commit:
>   "dtc: dt-check-style: Relax property ordering rules (drop alphabetical)"
> - Improve commit msg of "Unduplicate checks in
>   check_mixed_indent_chars()" patch.
> - Link to v2: https://patch.msgid.link/20260909-b4-dts-style-checker-continued-lines-v2-0-c5cb4c9d9b66@oss.qualcomm.com
> 
> Changes in v2:
> 1. Four new commits 1-4
> 2. Drop last commit
> v1: https://lore.kernel.org/all/20260906180437.166760-6-krzysztof.kozlowski@oss.qualcomm.com/
> 
> Best regards,
> Krzysztof
> 
> ---
> Krzysztof Kozlowski (7):
>       dtc: dt-check-style: Handle continued lines in check_hex_case()
>       dtc: dt-check-style: Handle continued lines in check_line_length()
>       dtc: dt-check-style: Handle continued lines in check_trailing_whitespace()
>       dtc: dt-check-style: Unduplicate checks in check_mixed_indent_chars()
>       dtc: dt-check-style: Right strip whitespaces, leftovers before comments
>       dtc: dt-check-style: Properly detect comments in multi-line properties
>       dtc: dt-check-style: Relax property ordering rules (drop alphabetical)

Patch 7 doesn't apply.

> base-commit: 694b801ceb1bea205878f2136e8b25c888e51be7

And I don't have this commit in my tree to resolve the conflicts.

Rob

  parent reply	other threads:[~2026-09-15 14:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09 13:10 [PATCH v3 0/7] dtc: dt-check-style: Improvements for handling continued lines Krzysztof Kozlowski
2026-09-09 13:10 ` [PATCH v3 1/7] dtc: dt-check-style: Handle continued lines in check_hex_case() Krzysztof Kozlowski
2026-09-09 13:10 ` [PATCH v3 2/7] dtc: dt-check-style: Handle continued lines in check_line_length() Krzysztof Kozlowski
2026-09-09 13:10 ` [PATCH v3 3/7] dtc: dt-check-style: Handle continued lines in check_trailing_whitespace() Krzysztof Kozlowski
2026-09-09 13:10 ` [PATCH v3 4/7] dtc: dt-check-style: Unduplicate checks in check_mixed_indent_chars() Krzysztof Kozlowski
2026-09-09 13:10 ` [PATCH v3 5/7] dtc: dt-check-style: Right strip whitespaces, leftovers before comments Krzysztof Kozlowski
2026-09-09 13:10 ` [PATCH v3 6/7] dtc: dt-check-style: Properly detect comments in multi-line properties Krzysztof Kozlowski
2026-09-09 13:10 ` [PATCH v3 7/7] dtc: dt-check-style: Relax property ordering rules (drop alphabetical) Krzysztof Kozlowski
2026-09-15 14:27 ` Rob Herring [this message]
2026-09-15 16:14   ` [PATCH v3 0/7] dtc: dt-check-style: Improvements for handling continued lines 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=20260915142742.GA1926857-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.