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  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, 12 May 2017 10:45:10 +0200
From:   SF Markus Elfring <>
To:     Julia Lawall <>
Cc:     Joe Perches <>,
        Dan Carpenter <>,
        Stephen Hemminger <>,
        Wolfram Sang <>,
        Haiyang Zhang <>,,
        LKML <>,
Subject: Re: Clarification for general change acceptance

> When you make a patch, you are not obliged to eliminate all of the other
> checkpatch warnings on the file.

Your view is generally fine.

> I don't know where you got this idea from.

I got used as a professional software developer to some approaches for
reducing development warnings to some degree. So I picked further update
suggestions up also from this source code analysis tool.


Powered by blists - more mailing lists