From: Robert Jarzmik <robert.jarzmik@free.fr>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] ARM: dts: intel: Drop pxa2xx
Date: Fri, 12 Dec 2025 22:58:16 +0100 [thread overview]
Message-ID: <m2345fmkg7.fsf@free.fr> (raw)
In-Reply-To: <20251212203226.458694-4-robh@kernel.org> (Rob Herring's message of "Fri, 12 Dec 2025 14:32:10 -0600")
"Rob Herring (Arm)" <robh@kernel.org> writes:
> These .dtsi files are not included anywhere in the tree and
> can't be
> tested. They have not been touched since 2018 other than
> clean-ups.
>
And yet, there are used by people using pxa2xx board with an DT
support
(like the mioa701 for which a board file was never merged).
If you remove pxa25x.dtsi and pxa27x.dtsi, you might as well
remove all
support for this architecture from the kernel, as these are the
building
blocks needed to make it work.
That might be what should be done, I'll let Arnd and Daniel
comment on
the future of PXA in the kernel.
Cheers.
--
Robert
--
Formal Signature
Emacs 25, org-mode 9, mu4e 1.0
next prev parent reply other threads:[~2025-12-12 21:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 20:32 [PATCH] ARM: dts: intel: Drop pxa2xx Rob Herring (Arm)
2025-12-12 21:58 ` Robert Jarzmik [this message]
2025-12-17 16:04 ` Arnd Bergmann
2025-12-18 8:21 ` Daniel
2025-12-22 22:04 ` Arnd Bergmann
2025-12-28 11:11 ` Robert Jarzmik
2025-12-31 0:02 ` Arnd Bergmann
2026-01-03 20:54 ` Robert Jarzmik
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=m2345fmkg7.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=daniel@zonque.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=gregory.clement@bootlin.com \
--cc=haojian.zhuang@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
/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).