From: Marek Vasut <marek.vasut@mailbox.org>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Marek Vasut <marek.vasut+renesas@mailbox.org>
Cc: linux-arm-kernel@lists.infradead.org,
Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 3/4] ARM: dts: renesas: r8a7740: Add ZT/ZTR trace clock on R-Mobile A1
Date: Mon, 27 Apr 2026 02:32:16 +0200 [thread overview]
Message-ID: <b3a8bf69-bdd2-4122-93c4-4c4d94240da4@mailbox.org> (raw)
In-Reply-To: <d246edd2-5f9d-4e95-850d-abff175088a6@kernel.org>
On 4/23/26 4:00 PM, Krzysztof Kozlowski wrote:
Hello Krzysztof,
>>>> "
>>>> WARNING: DT binding docs and includes should be a separate patch. See:
>>>> Documentation/devicetree/bindings/submitting-patches.rst
>>>
>>> So you did not implement it... Include goes with the binding. Always.
>>> Look at other commits.
>> The warning says the exact opposite thing , does it not ?
>>
>> Maybe the warning text needs to be updated ?
>
> The warning is shown for patches mixing stuff, like DTSI+header, so for
> this context the AND means binding doc plus header are separate FROM
> this patch. Not separate from each other.
Oh, thank you for the clarification.
> To me it is clear, so I don't feel like finding different text. If you
> find it unclear or confusing, you should propose something better.
How about this:
"
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 0d18771f1b013..715a98ccc69f7 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -2957,7 +2957,7 @@ sub process {
if (($last_binding_patch != -1) &&
($last_binding_patch ^
$is_binding_patch)) {
WARN("DT_SPLIT_BINDING_PATCH",
- "DT binding docs and
includes should be a separate patch. See:
Documentation/devicetree/bindings/submitting-patches.rst\n");
+ "DT binding docs and
includes should be a single patch, but separate from this patch. See:
Documentation/devicetree/bindings/submitting-patches.rst\n");
}
}
"
next prev parent reply other threads:[~2026-04-27 1:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 23:31 [PATCH v2 0/4] Describe coresight on R-Mobile A1 Marek Vasut
2026-04-15 23:31 ` [PATCH v2 1/4] dt-bindings: clock: renesas,cpg-clocks: Document ZT/ZTR trace clock " Marek Vasut
2026-04-21 8:01 ` Krzysztof Kozlowski
2026-04-22 23:33 ` Marek Vasut
2026-04-15 23:31 ` [PATCH v2 2/4] clk: renesas: r8a7740: Implement " Marek Vasut
2026-04-15 23:31 ` [PATCH v2 3/4] ARM: dts: renesas: r8a7740: Add " Marek Vasut
2026-04-21 8:02 ` Krzysztof Kozlowski
2026-04-22 23:33 ` Marek Vasut
2026-04-23 9:26 ` Krzysztof Kozlowski
2026-04-23 10:00 ` Marek Vasut
2026-04-23 14:00 ` Krzysztof Kozlowski
2026-04-27 0:32 ` Marek Vasut [this message]
2026-04-15 23:31 ` [PATCH v2 4/4] ARM: dts: renesas: r8a7740: Describe coresight " Marek Vasut
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=b3a8bf69-bdd2-4122-93c4-4c4d94240da4@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox