From: Krzysztof Kozlowski <krzk@kernel.org>
To: Conor Dooley <conor@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Cc: Bartosz Golaszewski <brgl@kernel.org>,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@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, robert.marko@sartura.hr,
daniel.machon@microchip.com, Steen.Hegelund@microchip.com
Subject: Re: [PATCH] arm64: Kconfig: provide a top-level switch for Microchip platforms
Date: Fri, 27 Feb 2026 11:37:23 +0100 [thread overview]
Message-ID: <c9df99ef-9bd6-43a0-9f22-721bd6bfc90c@kernel.org> (raw)
In-Reply-To: <20260227-wolverine-slogan-7af0661f6e44@spud>
On 27/02/2026 11:15, Conor Dooley wrote:
> On Fri, Feb 27, 2026 at 10:28:53AM +0100, Arnd Bergmann wrote:
>> 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.
>
> Here's the previous discussion when this was added not too long ago:
> https://lore.kernel.org/all/20250811122053.4bfyoefln7wpz2a4@DEN-DL-M70577/
>
> Daniel is probably the one that "needs" to answer this, I think the
> lan969x is added recently enough for this to not be particularly
> disruptive.
I don't get arguments there. The policy is one ARCH per vendor, so why
exactly upstream would like to "having more granular control with
separate"? That's downstream or vendor wishlist, not upstream.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-27 10:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 14:36 [PATCH] arm64: Kconfig: provide a top-level switch for Microchip platforms 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
2026-02-27 10:15 ` Conor Dooley
2026-02-27 10:37 ` Krzysztof Kozlowski [this message]
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=c9df99ef-9bd6-43a0-9f22-721bd6bfc90c@kernel.org \
--to=krzk@kernel.org \
--cc=Steen.Hegelund@microchip.com \
--cc=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=daniel.machon@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=robert.marko@sartura.hr \
--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