From: Olof Johansson <olof@lixom.net>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, soc@kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
open list <linux-kernel@vger.kernel.org>,
krzysztof.kozlowski@linaro.org, arnd@arndb.de,
Geert Uytterhoeven <geert@linux-m68k.org>,
william.zhang@broadcom.com, anand.gore@broadcom.com
Subject: Re: [PATCH v2 2/2] arm64: Kconfig.platforms: Group NXP platforms together
Date: Thu, 15 Sep 2022 09:08:28 -0700 [thread overview]
Message-ID: <YyNN/IZgOAlbSHnF@lx2k> (raw)
In-Reply-To: <20220829173830.3567047-3-f.fainelli@gmail.com>
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@gmail.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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-09-15 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 17:38 [PATCH v2 0/2] arm64: Kconfig.platforms: Group vendors together Florian Fainelli
2022-08-29 17:38 ` [PATCH v2 1/2] arm64: Kconfig.platforms: Re-organized Broadcom menu Florian Fainelli
2022-08-29 17:38 ` [PATCH v2 2/2] arm64: Kconfig.platforms: Group NXP platforms together Florian Fainelli
2022-09-15 16:08 ` Olof Johansson [this message]
2022-09-15 20:52 ` Florian Fainelli
2022-09-15 23:57 ` Olof Johansson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YyNN/IZgOAlbSHnF@lx2k \
--to=olof@lixom.net \
--cc=anand.gore@broadcom.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=f.fainelli@gmail.com \
--cc=geert@linux-m68k.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@kernel.org \
--cc=will@kernel.org \
--cc=william.zhang@broadcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).