Devicetree
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
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:19:51 +0200	[thread overview]
Message-ID: <aOjBp3bax6iJD_x4@shikoro> (raw)
In-Reply-To: <6ae23e44-2263-4cbe-aae1-d056597cd543@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]


> > 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 have it in DTS, then you need the binding. Just write it as much
> as complete as possible, mention incompleteness in binding description
> and provide reasons of incompleteness in commit msg.

Okay, that was my intention right away. So, I will do that, add
unevaluatedProperties and fix the spacing and we are good to go then?


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-10-10  8:19 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 [this message]
2025-10-10  8:22         ` 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=aOjBp3bax6iJD_x4@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --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=lee@kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@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