linux-kernel - Re: [PATCH] proc: Fix four errors in kmsg.c

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZLEH5AQKsfLfSxV7@alley>
Date:   Fri, 14 Jul 2023 10:31:32 +0200
From:   Petr Mladek <pmladek@...e.com>
To:     huzhi001@...suo.com
Cc:     tglx@...utronix.de, senozhatsky@...omium.org, adobriyan@...il.com,
        akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
        linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH] proc: Fix four errors in kmsg.c

On Fri 2023-07-14 10:22:48, Petr Mladek wrote:
> On Fri 2023-07-14 14:57:59, huzhi001@...suo.com wrote:
> > The following checkpatch errors are removed:
> > ERROR: "foo * bar" should be "foo *bar"
> > ERROR: "foo * bar" should be "foo *bar"
> > ERROR: "foo * bar" should be "foo *bar"
> > ERROR: "foo * bar" should be "foo *bar"
> 
> Please, do not do fix these cosmetic issues reported by checkpatch.pl.
> It is not worth the effort. In fact, it is contra productive.
> It complicates the git history, backports.

BTW, Did anyone suggest you to fix errors/warnings reported by
checkpatch.pl?

You seem to be 2nd person who sent similar patch from @suo.com
within the last week. The first patch was rejected as well,
see
https://lore.kernel.org/all/f2d8eb955890bc1db1b307db713d4a4a@208suo.com/

You might want to tell this person that there are better ways
how to get involved into the kernel development.

Best Regards,
Petr