From: Markus Heidelberg <M.Heidelberg@cab.de>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation: fix spelling, typos, grammar, duplicated words
Date: Fri, 26 Sep 2025 14:26:13 +0000 [thread overview]
Message-ID: <aNaic_817_R_SRd6@KAN23-025> (raw)
In-Reply-To: <875xd52y2z.fsf@trenco.lwn.net>
On Fri, Sep 26, 2025 at 06:32:52AM -0600, Jonathan Corbet wrote:
> Markus Heidelberg <m.heidelberg@cab.de> writes:
>
> > diff --git a/Documentation/kernel-hacking/hacking.rst b/Documentation/kernel-hacking/hacking.rst
> > index 0042776a9e17..b3d352d2ffcc 100644
> > --- a/Documentation/kernel-hacking/hacking.rst
> > +++ b/Documentation/kernel-hacking/hacking.rst
> > @@ -259,7 +259,7 @@ overruns. Make sure that will be enough.
> > .. note::
> >
> > You will know when you are a real kernel hacker when you start
> > - typoing printf as printk in your user programs :)
> > + typing printf as printk in your user programs :)
>
> This one, at least, is as intended and does not need to be "fixed".
Oh, I got that joke now :)
> For a future version, it would be better to split the patches apart and
> send them to the relevant maintainers.
I've scratched my head about the best approach a long time, looked at
typo git commits, followed mailing list discussion from Link: tags.
Found documentation patches like this across different subsystems and
also a reply about undesired one-liner typo patches.
So I thought, if not touching the technical content, using one combined
documentation patch might be a proper way.
Will have a look at splitting the patch up if not resulting in
one-liners only.
Markus
next prev parent reply other threads:[~2025-09-26 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 9:53 [PATCH] Documentation: fix spelling, typos, grammar, duplicated words Markus Heidelberg
2025-09-26 12:32 ` Jonathan Corbet
2025-09-26 14:26 ` Markus Heidelberg [this message]
2025-09-26 17:36 ` Randy Dunlap
2025-09-29 9:06 ` Markus Heidelberg
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=aNaic_817_R_SRd6@KAN23-025 \
--to=m.heidelberg@cab.de \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.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