From: "Arnd Bergmann" <arnd@arndb.de>
To: "Meghana Malladi" <m-malladi@ti.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>
Cc: "Bjorn Andersson" <quic_bjorande@quicinc.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, srk@ti.com,
"MD Danish Anwar" <danishanwar@ti.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>
Subject: Re: [EXTERNAL] Re: [PATCH] arm64: defconfig: Enable HSR driver
Date: Thu, 27 Feb 2025 08:32:00 +0100 [thread overview]
Message-ID: <d0303f33-3cde-45ca-8f25-313629bce863@app.fastmail.com> (raw)
In-Reply-To: <f1d61696-a5c0-4727-ab52-526294a2a5f9@ti.com>
On Thu, Feb 27, 2025, at 06:43, Malladi, Meghana wrote:
> On 2/26/2025 5:36 PM, Krzysztof Kozlowski wrote:
>> On 26/02/2025 12: 54, Malladi, Meghana wrote: > Hi Krzysztof, > > On
>> 2/26/2025 4: 18 PM, Krzysztof Kozlowski wrote: >> On 26/02/2025 11: 44,
>>
>> Yes, sure, but this defconfig change benefits and is sent for certain TI
>> upstream boards, so it is TI upstream maintainers field. It still fits
>> the "Submitting Patches for Given SoC" in SoC maintainer profile.
>>
>
> Okay, I got your point now. So as long as this defconfig benefits TI
> SoCs, it should be sent with maintainer profile. I will keep that in
> mind for future patches as well. Thanks for clarifying this.
It's mainly for practical reasons: the patches I put into the soc
tree usually come from platform maintainers that I'm already working
with. They understand the process and I generally trust their
judgement of what should go into the kernel or not.
Individual contributors can still send patches to soc@lists.linux.dev
(formerly soc@kernel.org) and I will usually end up merging them, but
that means that the patch itself needs a more elaborate justification
for why it should be merged, and I end up spending a bit more time on
figuring out if I should take it.
Arnd
prev parent reply other threads:[~2025-02-27 7:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 6:00 [PATCH] arm64: defconfig: Enable HSR driver Ravi Gunasekaran
2024-04-19 6:02 ` Arnd Bergmann
2024-04-19 6:25 ` Ravi Gunasekaran
2024-04-19 7:02 ` Arnd Bergmann
2025-02-26 6:14 ` Malladi, Meghana
2025-02-26 6:18 ` Malladi, Meghana
2025-02-26 7:45 ` Arnd Bergmann
2025-02-26 8:05 ` Krzysztof Kozlowski
2025-02-26 10:44 ` [EXTERNAL] " Malladi, Meghana
2025-02-26 10:48 ` Krzysztof Kozlowski
2025-02-26 11:54 ` Malladi, Meghana
2025-02-26 12:06 ` Krzysztof Kozlowski
2025-02-27 5:43 ` Malladi, Meghana
2025-02-27 7:32 ` Arnd Bergmann [this message]
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=d0303f33-3cde-45ca-8f25-313629bce863@app.fastmail.com \
--to=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=danishanwar@ti.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-malladi@ti.com \
--cc=quic_bjorande@quicinc.com \
--cc=srk@ti.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