linux-kernel - 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]

Date: Fri, 19 Apr 2024 09:02:36 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Ravi Gunasekaran" <r-gunasekaran@...com>,
 "Catalin Marinas" <catalin.marinas@....com>, "Will Deacon" <will@...nel.org>,
 "Nishanth Menon" <nm@...com>, "Vignesh Raghavendra" <vigneshr@...com>,
 "Tero Kristo" <kristo@...nel.org>
Cc: "Bjorn Andersson" <quic_bjorande@...cinc.com>,
 "Krzysztof Kozlowski" <krzysztof.kozlowski@...aro.org>,
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
 srk@...com
Subject: Re: [PATCH] arm64: defconfig: Enable HSR driver

On Fri, Apr 19, 2024, at 08:25, Ravi Gunasekaran wrote:
> On 4/19/24 11:32 AM, Arnd Bergmann wrote:
>> On Fri, Apr 19, 2024, at 08:00, Ravi Gunasekaran wrote:
>>> HSR is a redundancy protocol that can be realized with any
>>> two port ethernet controller.
>>>
>>> Many of TI's K3 SoCs support multi port ethernet controller.
>>> So enable HSR driver inorder to support this protocol on
>>> such SoCs.
>>>
>>> Signed-off-by: Ravi Gunasekaran <r-gunasekaran@...com>
>> 
>> Acked-by: Arnd Bergmann <arnd@...db.de>
>> 
>> The normal way this gets picked up into mainline is that you
>> send it to the K3 platform maintainers (added to Cc) and they
>> send me a pull request or forward the patch to soc@...nel.org.
>> 
>
> I usually do that for TI specific patches. This one seemed like a
> generic one as HSR protocol can be run on any multi port ethernet
> controller. So I wasn't sure about including TI maintainers. 
>
> But no harm in Cc'ing them. I will follow this advice for future
> patches.

Ah, I think I misread this as being much more hardware specific.
In a case like this, going through either a platform maintainer
or sending the patch directly to soc@...nel.org (with the usual
Ccs) is equally fine.

    Arnd