[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3dc9d86d-7b98-33ab-880e-a9584b8fac4b@gmail.com>
Date: Thu, 15 Sep 2022 13:52:12 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Olof Johansson <olof@...om.net>
Cc: linux-arm-kernel@...ts.infradead.org, soc@...nel.org,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
open list <linux-kernel@...r.kernel.org>,
krzysztof.kozlowski@...aro.org, arnd@...db.de,
Geert Uytterhoeven <geert@...ux-m68k.org>,
william.zhang@...adcom.com, anand.gore@...adcom.com
Subject: Re: [PATCH v2 2/2] arm64: Kconfig.platforms: Group NXP platforms
together
On 9/15/22 09:08, Olof Johansson wrote:
> On Mon, Aug 29, 2022 at 10:38:29AM -0700, Florian Fainelli wrote:
>> Group the three NXP platforms under an ARCH_NXP menuconfig symbol to
>> make make selection of similar vendor SoCs visually nicer.
>>
>> Signed-off-by: Florian Fainelli <f.fainelli@...il.com>
>
> Hi,
>
> While these are convenient if they're done right from the beginning, the result
> of adding a new dependency like this is that old defconfigs stop working if you
> just go with the default.
>
> Was there a reason to group these now and cause this config churn for
> downstream users?
No reason to cause churn, and no specific reason other than visually and
logically group options from the same vendors. I had clearly not
anticipated the defconfig breakage, too bad that Kconfig does not allow
menuconfig items to be enabled by default, or does it?
--
Florian
Powered by blists - more mailing lists