From: Randy Dunlap <rdunlap@infradead.org>
To: Antonio Borneo <antonio.borneo@foss.st.com>,
Arnd Bergmann <arnd@arndb.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: linux-sh@vger.kernel.org,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Vaibhav Hiremath <hvaibhav.linux@gmail.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
andrew.jones@linux.dev, Paul Cercueil <paul@crapouillou.net>,
Max Filippov <jcmvbkbc@gmail.com>,
linux-stm32@st-md-mailman.stormreply.com,
chrome-platform@lists.linux.dev, openbmc@lists.ozlabs.org,
x86@kernel.org, Andy Shevchenko <andy.shevchenko@gmail.com>,
Matti Vaittinen <mazziesaccount@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Paul Kocialkowski <paulk@sys-base.io>,
linux-sound@vger.kernel.org,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux-OMAP <linux-omap@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-mips@vger.kernel.org, asahi@lists.linux.dev,
Srinivas Kandagatla <srini@kernel.org>,
Jonathan Cameron <jic23@kernel.org>
Subject: Re: [Linux-stm32] Kconfig dangling references (BZ 216748)
Date: Sun, 4 Jan 2026 17:17:14 -0800 [thread overview]
Message-ID: <eb7c246a-6c5f-4d8d-bc96-2a71ece2e042@infradead.org> (raw)
In-Reply-To: <0220ec0592b6ef8936c25cffbc6cbfa0539fb71a.camel@foss.st.com>
On 12/8/25 1:48 AM, Antonio Borneo wrote:
> On Mon, 2025-12-08 at 09:55 +0100, Arnd Bergmann wrote:
>> On Mon, Dec 8, 2025, at 03:04, Randy Dunlap wrote:
>>> from https://bugzilla.kernel.org/show_bug.cgi?id=216748
>>>
>>> The bugzilla entry includes a Perl script and a shell script.
>>> This is the edited result of running them (I removed some entries that
>>> were noise).
>>>
>>> I'll try to Cc: all of the relevant mailing lists or individuals.
>>>
>>> ...
>>>
>>> MACH_STM32MP25 ---
>>> drivers/pinctrl/stm32/Kconfig:58: default MACH_STM32MP25 || (ARCH_STM32
>>> && ARM64)
>>
>> This was likely intended for 32-bit kernels on 64-bit STM32MP25
>> chips, which we don't support. I think this can go.
>
> Yes, I fully agree!
>
> I have a series pinctrl stm32 to be rebased on v6.19-rc1 and I can include the
> drop of MACH_STM32MP25 inside it.
and what about this dangling symbol?
arch/arm64/Kconfig.platforms:375: select ARM_SMC_MBOX
It was merged with ARCH_STM32 in
9e4e24414cc6 ("arm64: introduce STM32 family on Armv8 architecture")
Same answer as for MACH_STM32MP25?
If so, Antonio, can you take care of that one also, please?
thanks.
--
~Randy
next prev parent reply other threads:[~2026-01-05 1:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 2:04 Kconfig dangling references (BZ 216748) Randy Dunlap
2025-12-08 8:04 ` Matti Vaittinen
2025-12-08 8:55 ` Arnd Bergmann
2025-12-08 9:48 ` [Linux-stm32] " Antonio Borneo
2026-01-05 1:17 ` Randy Dunlap [this message]
2026-01-05 8:47 ` Antonio Borneo
2025-12-08 9:06 ` Takashi Iwai
2025-12-09 9:36 ` Richard Fitzgerald
2025-12-08 18:13 ` Paul Kocialkowski
2025-12-08 18:39 ` Randy Dunlap
2025-12-08 20:05 ` Janne Grunau
2025-12-10 22:09 ` Paul Kocialkowski
2025-12-10 13:06 ` Paul Cercueil
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=eb7c246a-6c5f-4d8d-bc96-2a71ece2e042@infradead.org \
--to=rdunlap@infradead.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrew.jones@linux.dev \
--cc=andy.shevchenko@gmail.com \
--cc=antonio.borneo@foss.st.com \
--cc=arnd@arndb.de \
--cc=asahi@lists.linux.dev \
--cc=chrome-platform@lists.linux.dev \
--cc=dri-devel@lists.freedesktop.org \
--cc=hvaibhav.linux@gmail.com \
--cc=jcmvbkbc@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mazziesaccount@gmail.com \
--cc=openbmc@lists.ozlabs.org \
--cc=p.zabel@pengutronix.de \
--cc=paul@crapouillou.net \
--cc=paulk@sys-base.io \
--cc=srini@kernel.org \
--cc=x86@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