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

Message-ID: <091ba604-d5a3-fe13-f13b-6b7e31ec63f6@gmail.com>
Date:   Sun, 25 Oct 2020 15:31:06 +0530
From:   Aditya <yashsri421@...il.com>
To:     Lukas Bulwahn <lukas.bulwahn@...il.com>,
        Joe Perches <joe@...ches.com>
Cc:     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 25/10/20 11:21 am, Lukas Bulwahn wrote:

> This is a nice idea as well. And I recommend to do this kind of research 
> looking at checkpatch and clang-format; both will not be the 'final tools' 
> but I think if you can identify a good mix and combination of those two 
> tools, we will get a good step forward of documenting the 
> commonalities and differences of coding styles in the different 
> subcommunities (the preferences of specific maintainers and subsystems).
> 
> A last nice idea to consider:
> 
> I would like to have an interactive checkpatch.pl mode where an authors
> can say that they ran checkpatch.pl, seen the warning and errors 
> reported, but disagree and comment why they disagree. Then this kind of
> information is added to the patch in a non-disturbing area of the patch
> and we can pick up and aggregate that information from the patches to see
> the complaints, false positives to address or suggestions which rules
> should be disabled for some subcommunities.
> 
> Aditya, your task is now to make those ideas more specific and write down 
> a one to two page project proposal for the mentorship. It can be to some 
> extent in bullet points as long as it is roughly understandable to all of 
> us what you plan and would like to do.
> 
> With that proposal accepted, you have shown to be applicable to the 
> mentorship program here and we take care of the last organisational points 
> before the start.
> 
> Lukas
> 

Alright Sir. I'll be sending my proposal in few days time, on the
basis of my formulated ideas.
Will let you know if I face any doubts during the procedure :)

Thanks
Aditya