linux-kernel - Re: [PATCH v2 1/3] Documentation: mcp16502-regulator: fix spelling mistake

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]

Date:   Fri, 27 Nov 2020 13:48:09 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Michael Klein <michael@...sekall.de>
Cc:     Andrei Stefanescu <andrei.stefanescu@...rochip.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Rob Herring <robh+dt@...nel.org>,
        Support Opensource <support.opensource@...semi.com>,
        Lee Jones <lee.jones@...aro.org>, linux-kernel@...r.kernel.org,
        trivial@...nel.org
Subject: Re: [PATCH v2 1/3] Documentation: mcp16502-regulator: fix spelling
 mistake

On Fri, Nov 27, 2020 at 01:52:00PM +0100, Michael Klein wrote:
> Signed-off-by: Michael Klein <michael@...sekall.de>
> ---
>   No changes in v2

Please do not submit new versions of already applied patches, please
submit incremental updates to the existing code.  Modifying existing
commits creates problems for other users building on top of those
commits so it's best practice to only change pubished git commits if
absolutely essential.

Please submit patches using subject lines reflecting the style for the
subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and
make sure your subject lines visually resemble what they're doing.
There's no need to resubmit to fix this alone.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)