linux-kernel - Re: [EXTERNAL] Re: [PATCH] arm64: defconfig: Enable HSR driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <d0303f33-3cde-45ca-8f25-313629bce863@app.fastmail.com>
Date: Thu, 27 Feb 2025 08:32:00 +0100
From: "Arnd Bergmann" <arnd@...db.de>
To: "Meghana Malladi" <m-malladi@...com>,
 "Krzysztof Kozlowski" <krzysztof.kozlowski@...aro.org>
Cc: "Bjorn Andersson" <quic_bjorande@...cinc.com>,
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
 srk@...com, "MD Danish Anwar" <danishanwar@...com>,
 "Catalin Marinas" <catalin.marinas@....com>, "Will Deacon" <will@...nel.org>
Subject: Re: [EXTERNAL] Re: [PATCH] arm64: defconfig: Enable HSR driver

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@...ts.linux.dev
(formerly soc@...nel.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