From: Rob Herring <robh@kernel.org>
To: Zev Weiss <zev@bewilderbeest.net>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Laxman Dewangan <ldewangan@nvidia.com>,
Patrick Rudolph <patrick.rudolph@9elements.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-kernel@vger.kernel.org,
Naresh Solanki <naresh.solanki@9elements.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, openbmc@lists.ozlabs.org,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH v2 2/3] dt-bindings: regulator: Add regulator-output binding
Date: Wed, 2 Nov 2022 11:40:58 -0500 [thread overview]
Message-ID: <166740725744.4016522.5256752936838143557.robh@kernel.org> (raw)
In-Reply-To: <20221031233704.22575-3-zev@bewilderbeest.net>
On Mon, 31 Oct 2022 16:37:03 -0700, Zev Weiss wrote:
> This describes a power output supplied by a regulator, such as a
> power outlet on a power distribution unit (PDU).
>
> Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
> ---
>
> Changes since v1:
> - removed 'regulator-leave-on' property
>
> .../bindings/regulator/regulator-output.yaml | 39 +++++++++++++++++++
> 1 file changed, 39 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/regulator/regulator-output.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-11-02 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 23:37 [PATCH v2 0/3] regulator: Add DT support for regulator-output connectors Zev Weiss
2022-10-31 23:37 ` [PATCH v2 1/3] regulator: devres: Add devm_regulator_bulk_get_exclusive() Zev Weiss
2022-10-31 23:37 ` [PATCH v2 2/3] dt-bindings: regulator: Add regulator-output binding Zev Weiss
2022-11-02 16:40 ` Rob Herring [this message]
2022-10-31 23:37 ` [PATCH v2 3/3] regulator: userspace-consumer: Handle regulator-output DT nodes Zev Weiss
2022-11-03 16:12 ` [PATCH v2 0/3] regulator: Add DT support for regulator-output connectors 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=166740725744.4016522.5256752936838143557.robh@kernel.org \
--to=robh@kernel.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=ldewangan@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.solanki@9elements.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick.rudolph@9elements.com \
--cc=robh+dt@kernel.org \
--cc=zev@bewilderbeest.net \
/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®