[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YyNN/IZgOAlbSHnF@lx2k>
Date: Thu, 15 Sep 2022 09:08:28 -0700
From: Olof Johansson <olof@...om.net>
To: Florian Fainelli <f.fainelli@...il.com>
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 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?
-Olof
Powered by blists - more mailing lists