From: Randy Dunlap <rdunlap@infradead.org>
To: Jonathan Corbet <corbet@lwn.net>, linux-kernel@vger.kernel.org
Cc: linux-doc@vger.kernel.org, Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH -next] docs: kdoc: various fixes for grammar, spelling, punctuation
Date: Tue, 8 Jul 2025 08:28:07 -0700 [thread overview]
Message-ID: <afe702b9-ec02-4c58-81e3-b4c244553e20@infradead.org> (raw)
In-Reply-To: <87qzyq6aeh.fsf@trenco.lwn.net>
On 7/8/25 7:10 AM, Jonathan Corbet wrote:
> Randy Dunlap <rdunlap@infradead.org> writes:
>
>> Correct grammar, spelling, and punctuation in comments, strings,
>> print messages, logs.
>>
>> Change two instances of two spaces between words to just one space.
>>
>> codespell was used to find misspelled words.
>>
>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>> Cc: Jonathan Corbet <corbet@lwn.net>
>> Cc: linux-doc@vger.kernel.org
>> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
>> ---
>> scripts/lib/kdoc/kdoc_files.py | 4 ++--
>> scripts/lib/kdoc/kdoc_output.py | 8 ++++----
>> scripts/lib/kdoc/kdoc_parser.py | 20 ++++++++++----------
>> scripts/lib/kdoc/kdoc_re.py | 24 ++++++++++++------------
>> 4 files changed, 28 insertions(+), 28 deletions(-)
>
> kdoc is kind of a moving target at the moment, so this patch doesn't
> really even come close to applying. Hold off for a bit, then regenerate
> against docs-next?
Sure, no problem.
--
~Randy
prev parent reply other threads:[~2025-07-08 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 5:01 [PATCH -next] docs: kdoc: various fixes for grammar, spelling, punctuation Randy Dunlap
2025-07-08 14:10 ` Jonathan Corbet
2025-07-08 15:28 ` Randy Dunlap [this message]
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=afe702b9-ec02-4c58-81e3-b4c244553e20@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.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;
as well as URLs for NNTP newsgroup(s).