From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Fabrice Gasnier <fabrice.gasnier@foss.st.com>, <robh+dt@kernel.org>
Cc: <olivier.moysan@foss.st.com>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH 0/2] ARM: dts: stm32: remove timer duplicate unit-address on stm32f7 series
Date: Mon, 14 Feb 2022 11:11:56 +0100 [thread overview]
Message-ID: <c3c1d310-19f0-889b-04b5-f3628e09b3bf@foss.st.com> (raw)
In-Reply-To: <1644403729-22665-1-git-send-email-fabrice.gasnier@foss.st.com>
Hi Fabrice
On 2/9/22 11:48, Fabrice Gasnier wrote:
> Remove a series of warnings seen when building with W=1, like:
> Warning (unique_unit_address): /soc/timer@40000c00: duplicate unit-address
> (also used in node /soc/timers@40000c00)
>
> This approach is based on some discussions[1], to restructure the dtsi
> and dts files.
> [1] https://lore.kernel.org/linux-arm-kernel/Yaf4jiZIp8+ndaXs@robh.at.kernel.org/
>
> arch/arm/boot/dts/stm32746g-eval.dts | 12 +++++++++
> arch/arm/boot/dts/stm32f746-disco.dts | 12 +++++++++
> arch/arm/boot/dts/stm32f746.dtsi | 47 -----------------------------------
> arch/arm/boot/dts/stm32f769-disco.dts | 12 +++++++++
> 4 files changed, 36 insertions(+), 47 deletions(-)
>
Series applied on stm32-next.
Cheers
Alex
prev parent reply other threads:[~2022-02-14 10:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 10:48 [PATCH 0/2] ARM: dts: stm32: remove timer duplicate unit-address on stm32f7 series Fabrice Gasnier
2022-02-09 10:48 ` [PATCH 1/2] ARM: dts: stm32: remove some " Fabrice Gasnier
2022-02-09 10:48 ` [PATCH 2/2] ARM: dts: stm32: remove timer5 " Fabrice Gasnier
2022-02-14 10:11 ` 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=c3c1d310-19f0-889b-04b5-f3628e09b3bf@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@foss.st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=olivier.moysan@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).