linux-kernel - Re: [PATCH v2] dt-bindings: remoteproc: Fix dead link to Keystone DSP GPIO binding

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 for Android: free password hash cracker in your pocket

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

Message-ID: <d2dfa83a-80e3-4a89-b853-a88589ef0092@gmail.com>
Date: Thu, 4 Dec 2025 00:26:50 +0530
From: Soham Metha <sohammetha01@...il.com>
To: Krzysztof Kozlowski <krzk@...nel.org>,
 linux-kernel-mentees@...ts.linuxfoundation.org
Cc: shuah@...nel.org, skhan@...uxfoundation.org,
 linux-kernel@...r.kernel.org, Bjorn Andersson <andersson@...nel.org>,
 Mathieu Poirier <mathieu.poirier@...aro.org>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, linux-remoteproc@...r.kernel.org,
 devicetree@...r.kernel.org
Subject: Re: [PATCH v2] dt-bindings: remoteproc: Fix dead link to Keystone DSP
 GPIO binding

Thank you for the feedback.

On 04/12/25 00:05, Krzysztof Kozlowski wrote:
> On 03/12/2025 19:03, Soham Metha wrote:
>> The old text binding 'gpio-dsp-keystone.txt' was replaced by a DT schema in
>> commit aff0a1701b020c8e6b172f28828fd4f3e6eed41a
> 
> Did you actually read what I asked? I think you just sent it too fast to
> be able to read entire multi-page document. If you read it, you would
> see that abbrev is 12 characters/digits.
> 

I did see the documentation mention that the abbreviation should use 
at least 12 characters, but I didn’t notice any upper limit mentioned 
in the text. Because of this wording, I assumed longer values were 
acceptable.

Should I send a v3 with a 12-character abbreviation?

>> ("dt-bindings: gpio: Convert ti,keystone-dsp-gpio to DT schema").
>>
>> Update the reference to point to the new file.
> 
> This wasn't here before, no need to add obvious statements.
> 
> Best regards,
> Krzysztof

--
Soham