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: <1513623831.31581.121.camel@perches.com>
Date:   Mon, 18 Dec 2017 11:03:51 -0800
From:   Joe Perches <joe@...ches.com>
To:     Knut Omang <knut.omang@...cle.com>,
        Leon Romanovsky <leon@...nel.org>
Cc:     linux-kernel@...r.kernel.org, Jason Gunthorpe <jgg@...pe.ca>,
        linux-rdma@...r.kernel.org, Doug Ledford <dledford@...hat.com>,
        Håkon Bugge <haakon.bugge@...cle.com>,
        Åsmund Østvold <asmund.ostvold@...cle.com>
Subject: Re: [PATCH v2 5/5] RDMA/core: Add runchecks.cfg for
 drivers/infiniband/core

On Mon, 2017-12-18 at 13:36 +0100, Knut Omang wrote:
> On Mon, 2017-12-18 at 10:02 +0200, Leon Romanovsky wrote:
[]
> > Also, I agree with other reviewers, there is no excuse for adding
> > checkpatch specifics per-subsystem/folder, the differences are better
> > to be treated in checkpatch.pl itself.

What other reviewers are those?

As a checkpatch maintainer, I don't believe it's appropriate
to add many per-subsystem specific rules to checkpatch.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ