From: "Arnd Bergmann" <arnd@arndb.de>
To: "Krzysztof Kozlowski" <krzk@kernel.org>,
"Bartosz Golaszewski" <brgl@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 10:28:53 +0100 [thread overview]
Message-ID: <244fdbad-0d9f-42bc-a005-5f5ef34d067d@app.fastmail.com> (raw)
In-Reply-To: <9132501f-76e9-46c0-839d-bde7246c3883@kernel.org>
On Fri, Feb 27, 2026, at 10:21, Krzysztof Kozlowski wrote:
> On 27/02/2026 09:51, Bartosz Golaszewski wrote:
>> On Fri, Feb 27, 2026 at 9:49 AM Arnd Bergmann <arnd@arndb.de> wrote:
> I don't think this is fixable, that's why I wrote that I accept the
> negative impact because I like the cleanup more.
Agreed. I remember when we split up the ethernet drivers into per-vendor
subdirectories and had to add 'default y' to each one in 88f07484ccdf
("drivers/net/ethernet/*: Enabled vendor Kconfig options"). Changing the
default to 'n' would be a regression now as much as it was then, so it's
not something we can expect to do more easily in the future.
If the Microchip maintainers think the change will cause too much
extra work, we can leave the current version forever, otherwise lets
apply it for 7.1.
Arnd
next prev parent reply other threads:[~2026-02-27 9:29 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
2026-02-27 8:51 ` Bartosz Golaszewski
2026-02-27 9:21 ` Krzysztof Kozlowski
2026-02-27 9:28 ` Arnd Bergmann [this message]
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=244fdbad-0d9f-42bc-a005-5f5ef34d067d@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®