From: Soham Metha <sohammetha01@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
linux-kernel-mentees@lists.linuxfoundation.org
Cc: shuah@kernel.org, skhan@linuxfoundation.org,
linux-kernel@vger.kernel.org,
Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: remoteproc: Fix dead link to Keystone DSP GPIO binding
Date: Thu, 4 Dec 2025 00:26:50 +0530 [thread overview]
Message-ID: <d2dfa83a-80e3-4a89-b853-a88589ef0092@gmail.com> (raw)
In-Reply-To: <aab83a61-9d22-443c-92bc-d7caf1c8afac@kernel.org>
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
next prev parent reply other threads:[~2025-12-03 18:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 18:03 [PATCH v2] dt-bindings: remoteproc: Fix dead link to Keystone DSP GPIO binding Soham Metha
2025-12-03 18:35 ` Krzysztof Kozlowski
2025-12-03 18:56 ` Soham Metha [this message]
2025-12-03 20:07 ` Krzysztof Kozlowski
2025-12-15 1:47 ` Mathieu Poirier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d2dfa83a-80e3-4a89-b853-a88589ef0092@gmail.com \
--to=sohammetha01@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=robh@kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox