From: Rob Herring <robh@kernel.org>
To: Sumit Semwal <sumit.semwal@linaro.org>
Cc: devicetree@vger.kernel.org, rnayak@codeaurora.org,
broonie@kernel.org, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, bjorn.andersson@linaro.org,
kgunda@codeaurora.org, lgirdwood@gmail.com, agross@kernel.org,
linux-arm-msm@vger.kernel.org, nishakumari@codeaurora.org
Subject: Re: [PATCH v5 2/4] dt-bindings: regulator: Add labibb regulator
Date: Thu, 9 Jul 2020 16:12:23 -0600 [thread overview]
Message-ID: <20200709221223.GA984064@bogus> (raw)
In-Reply-To: <20200622124110.20971-3-sumit.semwal@linaro.org>
On Mon, 22 Jun 2020 18:11:08 +0530, Sumit Semwal wrote:
> From: Nisha Kumari <nishakumari@codeaurora.org>
>
> Adding the devicetree binding for labibb regulator.
>
> Signed-off-by: Nisha Kumari <nishakumari@codeaurora.org>
> Signed-off-by: Sumit Semwal <sumit.semwal@linaro.org>
> [sumits: cleanup as per review comments and update to yaml]
>
> ---
> v5: Addressed review comments - removed interrupt-names, changed to
> dual license, added unevaluatedProperties: false
> v4: fixed dt_binding_check issues
> v3: moved to yaml
> v2: updated for better compatible string and names.
> ---
> .../regulator/qcom-labibb-regulator.yaml | 70 +++++++++++++++++++
> 1 file changed, 70 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/regulator/qcom-labibb-regulator.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-07-09 22:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 12:41 [PATCH v5 0/4] Qualcomm labibb regulator driver Sumit Semwal
2020-06-22 12:41 ` [PATCH v5 1/4] regulator: Allow regulators to verify enabled during enable() Sumit Semwal
2020-06-22 12:41 ` [PATCH v5 2/4] dt-bindings: regulator: Add labibb regulator Sumit Semwal
2020-07-09 22:12 ` Rob Herring [this message]
2020-06-22 12:41 ` [PATCH v5 3/4] arm64: dts: qcom: pmi8998: Add nodes for LAB and IBB regulators Sumit Semwal
2020-06-22 12:41 ` [PATCH v5 4/4] regulator: qcom: Add labibb driver Sumit Semwal
2020-07-15 14:59 ` [PATCH v5 0/4] Qualcomm labibb regulator driver 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=20200709221223.GA984064@bogus \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kgunda@codeaurora.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nishakumari@codeaurora.org \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=sumit.semwal@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.