linux-kernel - Re: [PATCH v3] checkpatch: fix false positives in REPEATED

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: <alpine.DEB.2.21.2010250708050.6697@felia>
Date:   Sun, 25 Oct 2020 07:11:40 +0100 (CET)
From:   Lukas Bulwahn <lukas.bulwahn@...il.com>
To:     Joe Perches <joe@...ches.com>
cc:     Lukas Bulwahn <lukas.bulwahn@...il.com>,
        Aditya <yashsri421@...il.com>, linux-kernel@...r.kernel.org,
        linux-kernel-mentees@...ts.linuxfoundation.org,
        dwaipayanray1@...il.com
Subject: Re: [PATCH v3] checkpatch: fix false positives in REPEATED_WORD
 warning

On Sat, 24 Oct 2020, Joe Perches wrote:

> On Sun, 2020-10-25 at 06:51 +0100, Lukas Bulwahn wrote:
> > We can identify a set of rules and clear automatic fixes that
> > maintainers can simply run this script over the patches they pick
> > up when they pick them up.
> 
> checkpatch --fix-inplace does that now.
> 
> But realistically, this is more an interactive bit that IMO
> should be a separate script on top of checkpatch.
>

Agree, and of course, we can work with some maintainers to find the best 
way to combine that into their 'pick up and apply patches' scripts?

E.g., some might be using b4 and we simply hook into that in a friendly 
way.

Further just documenting the potential options for maintainer in the 
maintainers handbook might also increase adoption.