From: Rob Herring <robh+dt@kernel.org>
To: Neil Armstrong <neil.armstrong@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Bjorn Andersson <andersson@kernel.org>,
Mark Brown <broonie@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Lee Jones <lee@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v5 1/2] dt-bindings: regulators: convert non-smd RPM Regulators bindings to dt-schema
Date: Sun, 8 Jan 2023 19:06:20 -0600 [thread overview]
Message-ID: <CAL_JsqLrDGW118vEV9dnpTkeJmE+S79u0WXajuTOVi31WmF87Q@mail.gmail.com> (raw)
In-Reply-To: <20221005-mdm9615-pinctrl-yaml-v5-1-910019fb8b9b@linaro.org>
On Thu, Nov 17, 2022 at 11:05 AM Neil Armstrong
<neil.armstrong@linaro.org> wrote:
>
> Convert the non-SMD Regulators bindings to dt-schema, the old text based
> bindings will be deleted later since the RPM bindings are not yet converted.
>
> Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
> Reviewed-by: Rob Herring <robh@kernel.org>
> ---
> .../bindings/regulator/qcom,rpm-regulator.yaml | 128 +++++++++++++++++++++
> 1 file changed, 128 insertions(+)
Looks like patch 2 was applied, but this one still needs to be respun
and applied as linux-next has warnings now.
Rob
next prev parent reply other threads:[~2023-01-09 1:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 17:04 [PATCH v5 0/2] arm: qcom: mdm9615: second round of bindings and DT fixes Neil Armstrong
2022-11-17 17:04 ` [PATCH v5 1/2] dt-bindings: regulators: convert non-smd RPM Regulators bindings to dt-schema Neil Armstrong
2022-11-17 23:49 ` Rob Herring
2023-01-09 1:06 ` Rob Herring [this message]
2023-01-09 10:48 ` Neil Armstrong
2022-11-17 17:04 ` [PATCH v5 2/2] dt-bindings: soc: qcom: convert non-smd RPM " Neil Armstrong
2022-12-28 2:41 ` (subset) [PATCH v5 0/2] arm: qcom: mdm9615: second round of bindings and DT fixes Bjorn Andersson
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=CAL_JsqLrDGW118vEV9dnpTkeJmE+S79u0WXajuTOVi31WmF87Q@mail.gmail.com \
--to=robh+dt@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@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.