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: <a3fc706c-3825-49fc-beea-3fea7d9c0038@linaro.org>
Date: Wed, 26 Feb 2025 13:06:16 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: "Malladi, Meghana" <m-malladi@...com>, Arnd Bergmann <arnd@...db.de>
Cc: quic_bjorande@...cinc.com, linux-arm-kernel@...ts.infradead.org,
 linux-kernel@...r.kernel.org, srk@...com,
 "Anwar, Md Danish" <danishanwar@...com>, catalin.marinas@....com,
 will@...nel.org
Subject: Re: [EXTERNAL] Re: [PATCH] arm64: defconfig: Enable HSR driver

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, Malladi, Meghana wrote: > > > On 2/26/2025 1: 35 
>> PM, Krzysztof Kozlowski wrote: >> On 26/02/2025 07: 18, Malladi, Meghana 
>> wrote: > Hi all, > > Apologies in >> case you are receiving this email
>> ZjQcmQRYFpfptBannerStart
>> This message was sent from outside of Texas Instruments.
>> Do not click links or open attachments unless you recognize the source 
>> of this email and know the content is safe.
>> Report Suspicious
>> <https://us-phishalarm-ewt.proofpoint.com/EWT/v1/G3vK! 
>> updq3RaPV007wGXFFrPD30z5a3GGYjpJweyhUcIfUTTaUs-8q0QpC4Yk9azBiFp7cBAf2Knk6fnVs4Fs-zRjTMEn8kmpiGo$>
>> ZjQcmQRYFpfptBannerEnd
>>
>> On 26/02/2025 11:44, Malladi, Meghana wrote:
>>>
>>>
>>> On 2/26/2025 1:35 PM, Krzysztof Kozlowski wrote:
>>>> On 26/02/2025 07: 18, Malladi, Meghana wrote: > Hi all, > > Apologies in 
>>>> case you are receiving this email for the second time. > Any reason why 
>>>> this patch hasn't been merged yet. Other than re-basing > this to the 
>>>> tip, anything
>>>> ZjQcmQRYFpfptBannerStart
>>>> This message was sent from outside of Texas Instruments.
>>>> Do not click links or open attachments unless you recognize the source 
>>>> of this email and know the content is safe.
>>>> Report Suspicious
>>>> <https://us-phishalarm-ewt.proofpoint.com/EWT/v1/G3vK! 
>>>> updgnZav1ue7gKXOnHOpH5hg8gLmw9Osqsqh- 
>>>> KTLRTnBEurV_VetrG7mzU898vB_5xFrYgbRkkuuFMBobM-uhFAmUgccRSk$>
>>>> ZjQcmQRYFpfptBannerEnd
>>>>
>>>> On 26/02/2025 07:18, Malladi, Meghana wrote:
>>>>> Hi all,
>>>>>
>>>>> Apologies in case you are receiving this email for the second time.
>>
>> BTW, Arnd when responded with Ack described the process.
>>
> 
> Yes, I wanted to re-confirm before posting it again (just in case).
> 
>>>>> Any reason why this patch hasn't been merged yet. Other than re-basing 
>>>>> this to the tip, anything else which needs to be addressed to get this 
>>>>> merged?
>>>>
>>>> I don't think you sent it to your platform maintainers, so no one would
>>>> apply it. Usually people ignore emails they did not receive, although I
>>>> am here an exception tracking missing-DT-patchwork things... :)
>>>>
>>>> Best regards,
>>>> Krzysztof
>>>>
>>>
>>> Hello Arnd/Krzysztof,
>>>
>>> Thank you for the replies :)
>>> Was having ambiguity since this is not TI specific change. Wanted to 
>>> confirm before re-posting. Will post v2 patch including TI platform 
>>> maintainers.
>>
>> It is not TI specific? Then which upstream boards benefit from this if
>> not TI?
>>
> 
> This change enables generic HSR protocol support in the kernel which is 
> required for HSR driver support in TI boards. When I said "not TI 
> specific" - I meant this change is not internal to TI driver. Hope this 
> clarifies the miscommunication from my earlier mail.

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.

Best regards,
Krzysztof