From: Linus Walleij <linus.walleij@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Patrice Chotard <patrice.chotard@foss.st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH 3/4] AMR: dts: st: ste: switch to enable-gpios
Date: Thu, 10 Aug 2023 10:02:03 +0200 [thread overview]
Message-ID: <CACRpkdZXUEh2cCyWaNyMnBot40DHQa0O8LPHOB14hpk8sXRM9w@mail.gmail.com> (raw)
In-Reply-To: <20230726070353.103989-3-krzysztof.kozlowski@linaro.org>
On Wed, Jul 26, 2023 at 9:03 AM Krzysztof Kozlowski
<krzysztof.kozlowski@linaro.org> wrote:
> The recommended name for enable GPIOs property in regulator-gpio is
> "enable-gpios". This is also required by bindings:
>
> ste-hrefv60plus-stuib.dtb: regulator-gpio: Unevaluated properties are not allowed ('enable-gpio' was unexpected)
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Hm if the subject start turning ARM: dts: st: ste: on these I might
need to consider
to move the ste(ricsson) stuff out of dts/st, this series mixes up the Ux500 and
st maintainers. I can deal with this one but if it confuses the scripts that's
not good.
Anyways, patch applied! (With subject fixed.)
Yours,
Linus Walleij
next prev parent reply other threads:[~2023-08-10 8:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 7:03 [PATCH 1/4] ARM: dts: st: stm32mp157c-emstamp: drop incorrect vref_ddr property Krzysztof Kozlowski
2023-07-26 7:03 ` [PATCH 2/4] ARM: dts: st: stm32mp157c-emstamp: correct regulator-active-discharge Krzysztof Kozlowski
2023-07-26 7:03 ` [PATCH 3/4] AMR: dts: st: ste: switch to enable-gpios Krzysztof Kozlowski
2023-07-30 17:48 ` Krzysztof Kozlowski
2023-08-10 8:02 ` Linus Walleij [this message]
2023-07-26 7:03 ` [PATCH 4/4] AMR: dts: st: stih407: drop max-duty-cycle Krzysztof Kozlowski
2023-08-04 15:37 ` Patrice CHOTARD
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=CACRpkdZXUEh2cCyWaNyMnBot40DHQa0O8LPHOB14hpk8sXRM9w@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--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=patrice.chotard@foss.st.com \
--cc=robh+dt@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).