From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bartosz Golaszewski <brgl@kernel.org>,
Daniel Machon <daniel.machon@microchip.com>
Cc: Conor Dooley <conor@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
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,
Steen.Hegelund@microchip.com
Subject: Re: [PATCH] arm64: Kconfig: provide a top-level switch for Microchip platforms
Date: Wed, 11 Mar 2026 09:58:22 +0100 [thread overview]
Message-ID: <d9f9884e-b4f4-4f38-9732-66ff90408b4d@kernel.org> (raw)
In-Reply-To: <CAMRc=MdrrzoL3r-Br2pvR=TXxXVdS_ouf1ikNysd=GuhR1V84g@mail.gmail.com>
On 11/03/2026 09:32, Bartosz Golaszewski wrote:
>>>>
>>>> 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
>>
>> The out-of-tree defconfig impact is minimal for us. As Conor mentioned, lan969x
>> was added fairly recently, so the number of affected users should be small.
>>
>> /Daniel
>
> So can this be picked up directly into ARM-SoC please?
This should go rather via Microchip ARM64 tree.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-11 8:58 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
2026-02-27 11:17 ` Daniel Machon
2026-03-11 8:32 ` Bartosz Golaszewski
2026-03-11 8:58 ` Krzysztof Kozlowski [this message]
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=d9f9884e-b4f4-4f38-9732-66ff90408b4d@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