linux-kernel - Re: [PATCH] docs: staging: fix typo in docs

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CAF2+nmZMOkti71ZZ6P1RB=4XYO5SHW2fA5hWscK0krqoP7Cyqw@mail.gmail.com>
Date: Fri, 9 Feb 2024 09:47:54 +0100
From: vincenzo mezzela <vincenzo.mezzela@...il.com>
To: Jonathan Corbet <corbet@....net>
Cc: andersson@...nel.org, mathieu.poirier@...aro.org, 
	linux-remoteproc@...r.kernel.org, linux-doc@...r.kernel.org, 
	linux-kernel@...r.kernel.org, skhan@...uxfoundation.org
Subject: Re: [PATCH] docs: staging: fix typo in docs

Il giorno gio 8 feb 2024 alle ore 23:42 Jonathan Corbet
<corbet@....net> ha scritto:

Hi Jon,

>
> Vincenzo Mezzela <vincenzo.mezzela@...il.com> writes:
>
> So your fix is fine, but I need to point out a couple of things with the
> changelog.
>
> > This patch resolves a spelling error in the documentation found
> > with codespell.
>
> If you look at Documentation/process/submitting-patches.rst, you'll see
> that changelog text should be phrased in the imperative mode; no "this
> patch".  I tend not to be too fussy about that, but some maintainers
> will reject a patch out of hand for that, so it's a good thing to learn
> to avoid.
>
> > It is submitted as part of my application to the "Linux Kernel Bug
> > Fixing Spring Unpaid 2024" mentorship program of the Linux Kernel
> > Foundation.
>
> This is interesting (I'd never heard of the Linux Kernel Foundation),

My mistake, I should have written LInux Foundation.

> but it's not really relevant for the kernel development history.  If you
> want to put this kind of information in a submission, put it after the
> "---" line so that it doesn't end up being committed with the patch.

Thank you very much for the corrections, I'm still in the process of
learning. I will pay more attention next time :)

>
> > Signed-off-by: Vincenzo Mezzela <vincenzo.mezzela@...il.com>
>
> I have gone ahead and fixed up these things and applied your two
> patches, thanks.

Thank you,
Vincenzo