From: Alexandre Torgue <alexandre.torgue@st.com>
To: Benjamin Gaignard <benjamin.gaignard@st.com>,
<mcoquelin.stm32@gmail.com>, <robh+dt@kernel.org>,
<mark.rutland@arm.com>
Cc: devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: stm32: Correct stmfx node name on stm32mp157c-ev1 board
Date: Mon, 10 Feb 2020 17:49:58 +0100 [thread overview]
Message-ID: <fb300410-7ee8-d199-9ffa-a91da0f80c8d@st.com> (raw)
In-Reply-To: <20200210134331.14039-2-benjamin.gaignard@st.com>
Hi Benjamin
On 2/10/20 2:43 PM, Benjamin Gaignard wrote:
> Change stmfx node name to fit with yaml requirements.
>
> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
> ---
> arch/arm/boot/dts/stm32mp157c-ev1.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/stm32mp157c-ev1.dts b/arch/arm/boot/dts/stm32mp157c-ev1.dts
> index 228e35e16884..ffd4e0caeedc 100644
> --- a/arch/arm/boot/dts/stm32mp157c-ev1.dts
> +++ b/arch/arm/boot/dts/stm32mp157c-ev1.dts
> @@ -210,7 +210,7 @@
> interrupt-parent = <&gpioi>;
> vdd-supply = <&v3v3>;
>
> - stmfx_pinctrl: stmfx-pin-controller {
> + stmfx_pinctrl: pinctrl {
> compatible = "st,stmfx-0300-pinctrl";
> gpio-controller;
> #gpio-cells = <2>;
>
Applied on stm32-next.
Thanks
Alex
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-02-10 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 13:43 [PATCH] ARM: dts: stm32: Correct stmfx node name on stm32746g-eval board Benjamin Gaignard
2020-02-10 13:43 ` [PATCH] ARM: dts: stm32: Correct stmfx node name on stm32mp157c-ev1 board Benjamin Gaignard
2020-02-10 16:49 ` Alexandre Torgue [this message]
2020-02-10 16:49 ` [PATCH] ARM: dts: stm32: Correct stmfx node name on stm32746g-eval board Alexandre Torgue
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=fb300410-7ee8-d199-9ffa-a91da0f80c8d@st.com \
--to=alexandre.torgue@st.com \
--cc=benjamin.gaignard@st.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.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).