From: Krzysztof Kozlowski <krzk@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: mfd: Add Renesas R2A11302FT PMIC
Date: Fri, 10 Oct 2025 10:22:04 +0200 [thread overview]
Message-ID: <dd99643e-8d53-440f-9415-1962c34a5d10@kernel.org> (raw)
In-Reply-To: <aOjBp3bax6iJD_x4@shikoro>
On 10/10/2025 10:19, Wolfram Sang wrote:
>
>>> Adding this PMIC to trivial devices would be my fav solution, actually.
>>
>> I meant, that not being complete is not yet problem.
>
> Ok, good.
>
>> Heh? I said your numbering is wrong. RFC was v1, this is v2.
>>
>> Your broken numbering breaks tools. Try yourself:
>>
>> b4 diff '<20251009181916.2431-2-wsa+renesas@sang-engineering.com>'
>
> I don't have b4, so I can't try. For 10+ years, I have been numbering
> like this: RFC, RFC v2, ...
>
> And once the patch leaves RFC status, switch to : PATCH, PATCH v2, ...
>
> It still makes sense to me and noone complained so far IIRC. I can
> switch to continous numbering if it makes other people happy.
If you carefully check responses from different people, you would see
complains about it. It's not logical, either. History of patch does not
disappear when transitioning from RFC to non-RFC. Previous reviews stay,
all previous comments are valid, all previous changelog is important so
is patch numbering. RFC is only indication you did not feel patch was ready.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-10-10 8:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 18:12 [PATCH] dt-bindings: mfd: Add Renesas R2A11302FT PMIC Wolfram Sang
2025-10-10 2:37 ` Krzysztof Kozlowski
2025-10-10 7:58 ` Wolfram Sang
2025-10-10 8:04 ` Krzysztof Kozlowski
2025-10-10 8:19 ` Wolfram Sang
2025-10-10 8:22 ` Krzysztof Kozlowski [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=dd99643e-8d53-440f-9415-1962c34a5d10@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh@kernel.org \
--cc=wsa+renesas@sang-engineering.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;
as well as URLs for NNTP newsgroup(s).