Re: [PATCH] arm64: Kconfig: provide a top-level switch for Microchip platforms

[Krzysztof Kozlowski <krzk@kernel.org>]

On 27/02/2026 09:51, Bartosz Golaszewski wrote:
> On Fri, Feb 27, 2026 at 9:49 AM Arnd Bergmann <arnd@arndb.de> wrote:
>>
>> On Fri, Feb 27, 2026, at 09:42, Bartosz Golaszewski wrote:
>>> On Thu, Feb 26, 2026 at 3:49 PM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>>>
>>>> This will surprise all out-of-tree non-defconfig users, because their
>>>> boards will stop working (drivers depend on ARCH_LAN969X|ARCH_SPARX5
>>>> which will be now disabled), but I like the consistency.
>>>>
>>>
>>> I'm not following, ARCH_SPARX5 remains enabled in defconfig and
>>> ARCH_LAN969X was already disabled by default.
>>
>> Your patch to the in-kernel defconfig is fine, but most users don't
>> use that but instead have their own defconfig files which they now
>> need to update.
>>
> 
> Ah ok, I see. Do you want me to do:
> 
> config ARCH_SPARX5
>     def_bool y if ARCH_MICROCHIP
> 
> ?
> 
> That should fix it, right?

No, because they still won't have ARCH_MICROCHIP. The out-of-tree
person's config is for example only:

CONFIG_ARCH_SPARX5=y

now, this will be silently discarded with all the drivers depending on
it, because the ARCH_MICROCHIP is missing.

I don't think this is fixable, that's why I wrote that I accept the
negative impact because I like the cleanup more.

Best regards,
Krzysztof