[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8f789104-f521-41ee-812b-34607f36a7da@kernel.org>
Date: Wed, 3 Dec 2025 21:07:08 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Soham Metha <sohammetha01@...il.com>,
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
On 03/12/2025 19:56, Soham Metha wrote:
> 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?
No need, this is just a nit.
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@....qualcomm.com>
Best regards,
Krzysztof
Powered by blists - more mailing lists