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: <alpine.DEB.2.21.1804230931050.6136@nanos.tec.linutronix.de>
Date:   Mon, 23 Apr 2018 09:34:19 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
cc:     LKML <linux-kernel@...r.kernel.org>,
        Philippe Ombredanne <pombredanne@...b.com>,
        Kate Stewart <kstewart@...uxfoundation.org>,
        Jonathan Corbet <corbet@....net>
Subject: Re: [patch 0/9] LICENSES: Add missing License Text and fixup bogus
 identifiers

On Mon, 23 Apr 2018, Greg Kroah-Hartman wrote:
> On Mon, Apr 23, 2018 at 12:02:08AM +0200, Thomas Gleixner wrote:
> > There are a few bogus SPDX identifiers in various files and SPDX
> > Identifiers used in tree or about to be used which have no corresponding
> > License Text file in the LICENSES directory or use the new variant of the
> > GPL-2.0[+] license identifiers which are not mentioned in the GPL-2.0
> > Valid-License-Identifiers: tags.
> > 
> > The following series cleans that up:
> > 
> >  - Use the proper identifiers
> > 
> >  - Add GPL-2.0-only and GPL-2.0-or-later identifiers to the GPL2.0 license
> > 
> >  - Add X11, Apache-2.0, CC-BY-SA-4.0, CCDL-1.0, Linux-OpenIB license texts
> >    to the LICENSES directory along with the required documentation texts
> 
> I'm thinking we need a script to keep these in check, right?  Does
> checkpatch.pl handle knowing what the "currently good" list of license
> tags are, or should we just use a separate script to parse the LICENSES/
> directory to get that list?

checkpatch.pl does not know about it. I have a python script which does the
parsing of the LICENSES directory and checks against every file in the
tree. I need to make that work with patches. I'm not sure whether
checkpatch.pl should grow all the parser knowledge, I guess it can just
invoke the script and be done with it.

Thanks,

	tglx

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ