linux-kernel - Re: [PATCH v2] Staging: nvec: nvec: fix double next comment

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: <4bff3adc94d909be7132151b1af211ed862b4126.camel@perches.com>
Date:   Sun, 27 Sep 2020 09:45:19 -0700
From:   Joe Perches <joe@...ches.com>
To:     Ryan Kosta <ryanpkosta@...il.com>, gregkh@...uxfoundation.org
Cc:     marvin24@....de, p.zabel@...gutronix.de, ac100@...ts.launchpad.net,
        linux-tegra@...r.kernel.org, devel@...verdev.osuosl.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] Staging: nvec: nvec: fix double next comment

On Sun, 2020-09-27 at 09:35 -0700, Ryan Kosta wrote:
> Changes since v1:
>  * Made commit message more clear
>  * Added description
> Note: previous patch named
>  "[PATCH] fix double next comment in drivers/staging/nvec/nvec.c"
> > 8------------------------------------------------------8<
> Fixes a comment typo.

Hi Ryan.

That comment should be _below_ the --- separator line

There's no need to double the nvec: word in the subject either.
And please use the imperative.

So the email message should look something like:

---------------------------------------------------------

From: <you>

Subject: [PATCH V2] staging: nvec: Remove repeated word typo in a comment

Fix a comment typo.

Signed-off-by: <you>
---

V2: Add a commit description

<patch>