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] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 9 Nov 2017 07:47:56 -0600
From:   Rob Herring <>
To:     Joe Perches <>
Cc:     Rob Herring <>,
        Linux Kernel Mailing List <>,
        Andy Whitcroft <>,
        Greg Kroah-Hartman <>
Subject: Re: [PATCH] Add SPDX license tag check

On Wed, Nov 8, 2017 at 8:10 PM, Joe Perches <> wrote:
> On Wed, 2017-11-08 at 19:10 -0600, Rob Herring wrote:
>> Add a check warning if SPDX-License-Identifier tags are not used in
>> newly added files.
> If this is to be done, and I think it's not a great idea,

Which part? SPDX tags or checking new files or just using checkpatch for this?

> there are better ways of doing this that emit this warning
> on a per-file basis instead of a per-patch.

You had mentioned using something like before. The
problem I see with that is few people run those tools. Lots of people
run We want this to be correct when added, not after
the fact by someone else who is not the author. It fits in the
workflow, because if checkpatch doesn't catch it, then I have to in

I do agree though that the implementation is a bit ugly given the line
by line way checkpatch works.


Powered by blists - more mailing lists