linux-kernel - Re: [PATCH] Documentation: fix spelling, typos, grammar, duplicated words

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aNaic_817_R_SRd6@KAN23-025>
Date: Fri, 26 Sep 2025 14:26:13 +0000
From: Markus Heidelberg <M.Heidelberg@....de>
To: Jonathan Corbet <corbet@....net>
CC: "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Documentation: fix spelling, typos, grammar, duplicated
 words

On Fri, Sep 26, 2025 at 06:32:52AM -0600, Jonathan Corbet wrote:
> Markus Heidelberg <m.heidelberg@....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