public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Support Opensource <support.opensource@diasemi.com>,
	Paul Cercueil <paul@crapouillou.net>,
	Adam Ward <Adam.Ward.opensource@diasemi.com>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] regulator: dt-bindings: dlg,da9121: add buck2 constraints
Date: Tue, 25 Jul 2023 21:00:28 +0100	[thread overview]
Message-ID: <20230725-pound-coil-4115d361864b@spud> (raw)
In-Reply-To: <20230725124629.150113-1-krzysztof.kozlowski@linaro.org>

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

On Tue, Jul 25, 2023 at 02:46:27PM +0200, Krzysztof Kozlowski wrote:
> Instead of describing the constraints for some devices (buck2 not
> present), code it in allOf:if:then section to actually allow validation
> of this requirement.
> 
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

Reviewed-by: Conor Dooley <conor.dooley@microchip.com>

Thanks,
Conor.

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

  parent reply	other threads:[~2023-07-25 20:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 12:46 [PATCH 1/3] regulator: dt-bindings: dlg,da9121: add buck2 constraints Krzysztof Kozlowski
2023-07-25 12:46 ` [PATCH 2/3] regulator: dt-bindings: dlg,da9121: allow different names Krzysztof Kozlowski
2023-07-25 12:46 ` [PATCH 3/3] regulator: dt-bindings: active-semi,act8846: correct supplies Krzysztof Kozlowski
2023-07-25 19:57   ` Conor Dooley
2023-07-25 20:00 ` Conor Dooley [this message]
2023-07-25 23:01 ` [PATCH 1/3] regulator: dt-bindings: dlg,da9121: add buck2 constraints Mark Brown

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=20230725-pound-coil-4115d361864b@spud \
    --to=conor@kernel.org \
    --cc=Adam.Ward.opensource@diasemi.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@crapouillou.net \
    --cc=robh+dt@kernel.org \
    --cc=support.opensource@diasemi.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