From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Josh Law" <objecting@objecting.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Tomás Pando" <tovictakamine@gmail.com>
Cc: skhan@linuxfoundation.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v3] docs: driver-api: fix 6 spelling typos in Documentation/driver-api
Date: Thu, 26 Mar 2026 10:34:17 +0100 [thread overview]
Message-ID: <f204211d-270c-47be-86c5-970cec55d94c@kernel.org> (raw)
In-Reply-To: <A54D6856-52DB-4914-BE50-A86EA76733CD@objecting.org>
On 24/03/2026 18:19, Josh Law wrote:
>
>
> On 24 March 2026 17:10:05 GMT, Jonathan Corbet <corbet@lwn.net> wrote:
>> Josh Law <objecting@objecting.org> writes:
>>
>>> Acked-By: Josh Law <objecting@objecting.org>
>>>
>>> Patches like these are good clarification
>>>
>>> Keep it up!
>>
>> I'm all for encouraging contributors, but an Acked-by from a random
>> contributor to a typo-fix patch, without having even bothered to trim
>> 100 lines of stuff, is not particularly helpful for maintainers. What
>> is your purpose here?
>>
>> Thanks,
>>
>> jon
>>
>
>
>
> Apologies Jon, I just like patches that fix typos, because when maintainers (or others..) have to read the code in let's say, 10 years, they will be able to understand the code easier.
>
You have been asked like 10 or 20 times already to adjust to mailing
list style of replies. No improvements.
You did not get the point here about your Ack. You answered why the
patch is right, but that was not the question. Question was what is the
purpose of your Ack?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-26 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 16:36 [PATCH v3] docs: driver-api: fix 6 spelling typos in Documentation/driver-api Tomás Pando
2026-03-24 16:44 ` Jonathan Corbet
2026-03-24 16:54 ` Josh Law
2026-03-24 17:10 ` Jonathan Corbet
2026-03-24 17:19 ` Josh Law
2026-03-26 9:34 ` Krzysztof Kozlowski [this message]
2026-03-25 18:36 ` Jonathan Corbet
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=f204211d-270c-47be-86c5-970cec55d94c@kernel.org \
--to=krzk@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=objecting@objecting.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=tovictakamine@gmail.com \
/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