From: Marek Vasut <marek.vasut@mailbox.org>
To: Joe Perches <joe@perches.com>, devicetree@vger.kernel.org
Cc: Andy Whitcroft <apw@canonical.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Rob Herring <robh@kernel.org>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] checkpatch: Update DT bindings should be a separate patch text
Date: Sat, 2 May 2026 23:03:07 +0200 [thread overview]
Message-ID: <09730fa3-ae28-4b4f-968c-e62a0a027159@mailbox.org> (raw)
In-Reply-To: <bb99f0086fc62bc09af132a41fdc8e874ed05a14.camel@perches.com>
On 5/2/26 10:03 PM, Joe Perches wrote:
> On Sat, 2026-05-02 at 21:10 +0200, Marek Vasut wrote:
>> The current message can be slightly misleading, because it triggers
>> on a patchset which contains the following sequence of patches, even
>> if the bindings and headers are clearly a separate patch:
>
> I agree with Krzysztof, I don't find the existing text unclear.
I guess it is just me who was confused my the output then.
prev parent reply other threads:[~2026-05-02 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-02 19:10 [PATCH] checkpatch: Update DT bindings should be a separate patch text Marek Vasut
2026-05-02 20:03 ` Joe Perches
2026-05-02 21:03 ` Marek Vasut [this message]
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=09730fa3-ae28-4b4f-968c-e62a0a027159@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=apw@canonical.com \
--cc=devicetree@vger.kernel.org \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=robh@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