Received-SPF: pass (google.com: domain of linux-kernel+bounces-151080-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Feedback-ID: i56a14606:Fastmail
User-Agent: Cyrus-JMAP/3.11.0-alpha0-379-gabd37849b7-fm-20240408.001-gabd37849
Precedence: bulk
MIME-Version: 1.0
Message-Id: <4c448e78-11e8-497b-8e98-c227b9fa273e@app.fastmail.com>
In-Reply-To: <2bcdf17c-c640-7c87-88eb-f465f8c78263@ti.com>
References: <20240419060013.14909-1-r-gunasekaran@ti.com>
 <4d63cbaa-63d9-49fa-bbf0-b3bc62ebfb36@app.fastmail.com>
 <2bcdf17c-c640-7c87-88eb-f465f8c78263@ti.com>
Date: Fri, 19 Apr 2024 09:02:36 +0200
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Ravi Gunasekaran" <r-gunasekaran@ti.com>,
 "Catalin Marinas" <catalin.marinas@arm.com>, "Will Deacon" <will@kernel.org>,
 "Nishanth Menon" <nm@ti.com>, "Vignesh Raghavendra" <vigneshr@ti.com>,
 "Tero Kristo" <kristo@kernel.org>
Cc: "Bjorn Andersson" <quic_bjorande@quicinc.com>,
 "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
 linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org,
 srk@ti.com
Subject: Re: [PATCH] arm64: defconfig: Enable HSR driver
Content-Type: text/plain

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@ti.com>
>> 
>> Acked-by: Arnd Bergmann <arnd@arndb.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@kernel.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@kernel.org (with the usual
Ccs) is equally fine.

    Arnd