From: Marek Vasut <marex@denx.de>
To: Conor Dooley <conor@kernel.org>,
Patrick DELAUNAY <patrick.delaunay@foss.st.com>
Cc: Alexandre TORGUE <alexandre.torgue@foss.st.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Pascal Paillet <p.paillet@foss.st.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH v3 1/2] dt-bindings: regulator: st,stm32mp1-pwr-reg: add compatible for STM32MP13
Date: Wed, 15 May 2024 17:37:49 +0200 [thread overview]
Message-ID: <9de93cbb-5868-473e-8b32-a6b6f50e128e@denx.de> (raw)
In-Reply-To: <20240515-monsoon-starfish-0dc59707e843@spud>
On 5/15/24 5:35 PM, Conor Dooley wrote:
> On Wed, May 15, 2024 at 04:33:22PM +0200, Patrick DELAUNAY wrote:
>> with
>>
>> compatible:
>> oneOf:
>> - items:
>> - const: st,stm32mp1,pwr-reg
>> - items:
>> - const: st,stm32mp13-pwr-reg
>> - const: st,stm32mp1,pwr-reg
>
> Other than the extra ,s this looks okay, thanks.
I think the extra ,s are actually correct, those are the ones from the
original compatible which had TWO ,s (it does look a bit unusual).
next prev parent reply other threads:[~2024-05-15 15:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 9:56 [PATCH v3 0/2] ARM: st: add new compatible for PWR regulators on STM32MP13 Patrick Delaunay
2024-05-13 9:56 ` [PATCH v3 1/2] dt-bindings: regulator: st,stm32mp1-pwr-reg: add compatible for STM32MP13 Patrick Delaunay
2024-05-13 14:34 ` Marek Vasut
2024-05-13 15:16 ` Conor Dooley
2024-05-13 18:02 ` Patrick DELAUNAY
2024-05-14 20:08 ` Conor Dooley
2024-05-15 14:33 ` Patrick DELAUNAY
2024-05-15 15:35 ` Conor Dooley
2024-05-15 15:37 ` Marek Vasut [this message]
2024-05-15 16:15 ` Conor Dooley
2024-05-16 16:32 ` Patrick DELAUNAY
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=9de93cbb-5868-473e-8b32-a6b6f50e128e@denx.de \
--to=marex@denx.de \
--cc=alexandre.torgue@foss.st.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=p.paillet@foss.st.com \
--cc=patrick.delaunay@foss.st.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;
as well as URLs for NNTP newsgroup(s).