From: "Arnd Bergmann" <arnd@arndb.de>
To: "Bartosz Golaszewski" <brgl@kernel.org>,
"Krzysztof Kozlowski" <krzk@kernel.org>
Cc: "Bartosz Golaszewski" <bartosz.golaszewski@oss.qualcomm.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>,
"Conor Dooley" <conor@kernel.org>,
"Nicolas Ferre" <nicolas.ferre@microchip.com>,
"Claudiu Beznea" <claudiu.beznea@tuxon.dev>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: Kconfig: provide a top-level switch for Microchip platforms
Date: Fri, 27 Feb 2026 09:48:43 +0100 [thread overview]
Message-ID: <10bb25d3-2f46-4b62-affb-31257d51e24f@app.fastmail.com> (raw)
In-Reply-To: <CAMRc=MehMLoBL573cWjQNN2eCiTCyqCv1xwVKqfkZ5isBhBUaA@mail.gmail.com>
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.
Arnd
next prev parent reply other threads:[~2026-02-27 8:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 14:36 Bartosz Golaszewski
2026-02-26 14:49 ` Krzysztof Kozlowski
2026-02-27 8:42 ` Bartosz Golaszewski
2026-02-27 8:48 ` Arnd Bergmann [this message]
2026-02-27 8:51 ` Bartosz Golaszewski
2026-02-27 9:21 ` Krzysztof Kozlowski
2026-02-27 9:28 ` Arnd Bergmann
2026-02-27 10:15 ` Conor Dooley
2026-02-27 10:37 ` Krzysztof Kozlowski
2026-02-27 11:17 ` Daniel Machon
2026-03-11 8:32 ` Bartosz Golaszewski
2026-03-11 8:58 ` Krzysztof Kozlowski
2026-03-18 8:21 ` Bartosz Golaszewski
2026-03-18 8:59 ` claudiu beznea
2026-02-27 9:19 ` Krzysztof Kozlowski
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=10bb25d3-2f46-4b62-affb-31257d51e24f@app.fastmail.com \
--to=arnd@arndb.de \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=will@kernel.org \
/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
all inboxes | Powered by JetHome®