From: Alexandre Torgue <alexandre.torgue@st.com>
To: Erwan Le Ray <erwan.leray@st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: devicetree@vger.kernel.org, bich.hemon@st.com,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: stm32: fix -Wall W=1 compilation warnings for can1_sleep pinctrl
Date: Fri, 26 Jul 2019 18:27:01 +0200 [thread overview]
Message-ID: <8cb628b9-dbbf-98d6-e09a-2ecc082315d4@st.com> (raw)
In-Reply-To: <1561972686-23281-1-git-send-email-erwan.leray@st.com>
Hi Erwan
On 7/1/19 11:18 AM, Erwan Le Ray wrote:
> Fix compilations warnings detected by -Wall W=1 compilation option:
> - node has a unit name, but no reg property
>
> Signed-off-by: Erwan Le Ray <erwan.leray@st.com>
>
> diff --git a/arch/arm/boot/dts/stm32mp157-pinctrl.dtsi b/arch/arm/boot/dts/stm32mp157-pinctrl.dtsi
> index 140a983..ce98fd8 100644
> --- a/arch/arm/boot/dts/stm32mp157-pinctrl.dtsi
> +++ b/arch/arm/boot/dts/stm32mp157-pinctrl.dtsi
> @@ -427,7 +427,7 @@
> };
> };
>
> - m_can1_sleep_pins_a: m_can1-sleep@0 {
> + m_can1_sleep_pins_a: m_can1-sleep-0 {
> pins {
> pinmux = <STM32_PINMUX('H', 13, ANALOG)>, /* CAN1_TX */
> <STM32_PINMUX('I', 9, ANALOG)>; /* CAN1_RX */
>
Thanks for cleaning the STM32 DT. Applied on stm32-next. Note that I
changed commit title to indicate which STM32 platform is targeted by
this patch.
Regards
Alex
prev parent reply other threads:[~2019-07-26 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 9:18 [PATCH] ARM: dts: stm32: fix -Wall W=1 compilation warnings for can1_sleep pinctrl Erwan Le Ray
2019-07-26 16:27 ` Alexandre Torgue [this message]
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=8cb628b9-dbbf-98d6-e09a-2ecc082315d4@st.com \
--to=alexandre.torgue@st.com \
--cc=bich.hemon@st.com \
--cc=devicetree@vger.kernel.org \
--cc=erwan.leray@st.com \
--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).