On Sun, 2026-01-04 at 17:17 -0800, Randy Dunlap wrote: > > > 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?
Sure, I can take care of it. But probably not in the same series for pinctrl. Regards, Antonio
