From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Woodrow Douglass <wdouglass@carnegierobotics.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 2/2] regulator: pf530x: dt-bindings: nxp,pf530x-regulator
Date: Thu, 4 Sep 2025 12:33:24 +0100 [thread overview]
Message-ID: <c4402946-9b76-4e1f-9a03-e5985cb023a3@sirena.org.uk> (raw)
In-Reply-To: <997eb50b-db3e-4c0e-be29-0d04fef73ccf@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 639 bytes --]
On Thu, Sep 04, 2025 at 07:44:57AM +0200, Krzysztof Kozlowski wrote:
> On 03/09/2025 22:03, Woodrow Douglass wrote:
> > +properties:
> > + compatible:
> > + enum:
> > + - nxp,pf5300
> > + - nxp,pf5301
> > + - nxp,pf5302
> Still compatibility not expressed.
> Please respond to comments.
He did reply to this in the cover letter (possibly for v3?) explaining
that he couldn't understand what you are talking about, the devices have
the same register interface but differ in the rated current. TBH I
can't really understand what the issue is either, perhaps if you could
suggest a concrete change you're looking for?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-09-04 11:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 20:03 [PATCH v4 0/2] regulator: pf530x: NXP PF530x regulator driver Woodrow Douglass
2025-09-03 20:03 ` [PATCH v4 1/2] regulator: pf530x: Add a driver for the NXP PF5300 Regulator Woodrow Douglass
2025-09-04 5:44 ` Krzysztof Kozlowski
2025-09-03 20:03 ` [PATCH v4 2/2] regulator: pf530x: dt-bindings: nxp,pf530x-regulator Woodrow Douglass
2025-09-03 23:27 ` Rob Herring (Arm)
2025-09-04 5:44 ` Krzysztof Kozlowski
2025-09-04 11:33 ` Mark Brown [this message]
2025-09-04 12:58 ` Woody Douglass
2025-09-04 13:05 ` 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=c4402946-9b76-4e1f-9a03-e5985cb023a3@sirena.org.uk \
--to=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=wdouglass@carnegierobotics.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
all inboxes | Powered by JetHome®