From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: "Rob Herring (Arm)" <robh@kernel.org>,
Viresh Kumar <vireshk@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>
Cc: <linux-arm-kernel@lists.infradead.org>, <soc@lists.linux.dev>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH v2] arm/arm64: dts: st: Drop unused .dtsi
Date: Fri, 16 Jan 2026 17:31:30 +0100 [thread overview]
Message-ID: <7c380ade-97df-4908-b571-d08e5437c72e@foss.st.com> (raw)
In-Reply-To: <20260113201340.36950-1-robh@kernel.org>
Hi Rob
On 1/13/26 21:13, Rob Herring (Arm) wrote:
> These .dtsi files are not included anywhere in the tree and can't be
> tested.
>
> Reviewed-by: Alexandre Torgue <alexandre.torgue@foss.st.com>
> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
> ---
> v2:
> - Drop erroneous QCom .dtsi
> ---
> arch/arm/boot/dts/st/spear320s.dtsi | 24 -------
> .../boot/dts/st/stm32mp15xxab-pinctrl.dtsi | 57 ---------------
> arch/arm64/boot/dts/st/stm32mp21xc.dtsi | 8 ---
> arch/arm64/boot/dts/st/stm32mp23xc.dtsi | 8 ---
> arch/arm64/boot/dts/st/stm32mp25xc.dtsi | 8 ---
> .../boot/dts/st/stm32mp25xxal-pinctrl.dtsi | 71 -------------------
> 6 files changed, 176 deletions(-)
> delete mode 100644 arch/arm/boot/dts/st/spear320s.dtsi
> delete mode 100644 arch/arm/boot/dts/st/stm32mp15xxab-pinctrl.dtsi
> delete mode 100644 arch/arm64/boot/dts/st/stm32mp21xc.dtsi
> delete mode 100644 arch/arm64/boot/dts/st/stm32mp23xc.dtsi
> delete mode 100644 arch/arm64/boot/dts/st/stm32mp25xc.dtsi
> delete mode 100644 arch/arm64/boot/dts/st/stm32mp25xxal-pinctrl.dtsi
>
Applied on stm32-next.
Thanks
prev parent reply other threads:[~2026-01-16 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 20:13 [PATCH v2] arm/arm64: dts: st: Drop unused .dtsi Rob Herring (Arm)
2026-01-15 4:11 ` Viresh Kumar
2026-01-16 16:31 ` 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=7c380ade-97df-4908-b571-d08e5437c72e@foss.st.com \
--to=alexandre.torgue@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=mcoquelin.stm32@gmail.com \
--cc=robh@kernel.org \
--cc=soc@lists.linux.dev \
--cc=vireshk@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