linux-kernel - Re: [PATCH v6] checkpatch.pl: Add SPDX license tag check

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]

Date:   Fri, 2 Feb 2018 17:12:46 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Igor Stoppa <igor.stoppa@...wei.com>
Cc:     Rob Herring <robh@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        linux-kernel@...r.kernel.org, Joe Perches <joe@...ches.com>,
        Andy Whitcroft <apw@...onical.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Philippe Ombredanne <pombredanne@...b.com>
Subject: Re: [PATCH v6] checkpatch.pl: Add SPDX license tag check

On Fri, Feb 02, 2018 at 05:49:20PM +0200, Igor Stoppa wrote:
> On 02/02/18 17:40, Rob Herring wrote:
> > Add SPDX license tag check based on the rules defined in
> 
> Shouldn't it also check that the license is compatible?

Baby steps please :)

> [...]
> 
> > +				} elsif ($realfile =~ /\.rst$/) {
> > +					$comment = '..';
> 
> What is the correct/acceptable license for documentation?
> Creative Commons? AFAIK GPL is for source code.
> 
> Googling didn't bring the wished-for enlightenment.

It depends on what you want to allow the documentation to be used for.
It's not a simple answer :(

thanks,

greg k-h