[PATCH] arm64: Kconfig: provide a top-level switch for Microchip platforms
claudiu beznea
claudiu.beznea at tuxon.dev
Wed Mar 18 01:59:55 PDT 2026
On 3/18/26 10:21, Bartosz Golaszewski wrote:
> On Wed, Mar 11, 2026 at 9:58 AM Krzysztof Kozlowski <krzk at kernel.org> wrote:
>>
>> On 11/03/2026 09:32, Bartosz Golaszewski wrote:
>>>>>>
>>>>>> Here's the previous discussion when this was added not too long ago:
>>>>>> https://lore.kernel.org/all/20250811122053.4bfyoefln7wpz2a4@DEN-DL-M70577/
>>>>>>
>>>>>> Daniel is probably the one that "needs" to answer this, I think the
>>>>>> lan969x is added recently enough for this to not be particularly
>>>>>> disruptive.
>>>>>
>>>>> I don't get arguments there. The policy is one ARCH per vendor, so why
>>>>> exactly upstream would like to "having more granular control with
>>>>> separate"? That's downstream or vendor wishlist, not upstream.
>>>>>
>>>>>
>>>>> Best regards,
>>>>> Krzysztof
>>>>
>>>> The out-of-tree defconfig impact is minimal for us. As Conor mentioned, lan969x
>>>> was added fairly recently, so the number of affected users should be small.
>>>>
>>>> /Daniel
>>>
>>> So can this be picked up directly into ARM-SoC please?
>>
>> This should go rather via Microchip ARM64 tree.
>>
>
> Hey Microchip maintainers, can you please pick it up for v7.1?
Applied to microchip-soc, thanks!
Will push it later today (infrastructure issue ATM).
Thank you,
Claudiu
More information about the linux-arm-kernel
mailing list