From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Mateusz Nowicki <mateusz.nowicki@posteo.net>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Olivier Moysan <olivier.moysan@foss.st.com>,
Amelie Delaunay <amelie.delaunay@foss.st.com>,
<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 0/2] arm64: dts: st: fix sai3b unit address on stm32mp2
Date: Mon, 28 Sep 2026 15:07:35 +0200 [thread overview]
Message-ID: <a4c02a71-df8e-4370-8ec5-9f07210f8727@foss.st.com> (raw)
In-Reply-To: <20260924193759.27881-1-mateusz.nowicki@posteo.net>
Hi
On 9/24/26 21:38, Mateusz Nowicki wrote:
> The sai3b node on stm32mp251 and stm32mp231 has a unit address taken
> from the secure alias of SAI3, while its reg property and all other SAI
> nodes use the non-secure alias. The reg property is correct, so there
> is no functional change.
>
> The typo comes from two different commits, so each SoC gets its own
> patch with its own Fixes tag.
>
> Mateusz Nowicki (2):
> arm64: dts: st: fix sai3b unit address on stm32mp251
> arm64: dts: st: fix sai3b unit address on stm32mp231
>
> arch/arm64/boot/dts/st/stm32mp231.dtsi | 2 +-
> arch/arm64/boot/dts/st/stm32mp251.dtsi | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
>
> base-commit: 2f92d900f262a16c8ae02daf53ae2910d07185f5
Applied on stm32-next.
thanks
Alex
prev parent reply other threads:[~2026-09-28 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 19:38 [PATCH 0/2] arm64: dts: st: fix sai3b unit address on stm32mp2 Mateusz Nowicki
2026-09-24 19:38 ` [PATCH 1/2] arm64: dts: st: fix sai3b unit address on stm32mp251 Mateusz Nowicki
2026-09-24 19:38 ` [PATCH 2/2] arm64: dts: st: fix sai3b unit address on stm32mp231 Mateusz Nowicki
2026-09-28 13:07 ` 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=a4c02a71-df8e-4370-8ec5-9f07210f8727@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=amelie.delaunay@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mateusz.nowicki@posteo.net \
--cc=mcoquelin.stm32@gmail.com \
--cc=olivier.moysan@foss.st.com \
--cc=robh@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).