linux-kernel - Re: [patch 0/2] LICENSES: Fix fallout from recent SPDX conversions

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: <20190116145618.6b8e8a81@lwn.net>
Date:   Wed, 16 Jan 2019 14:56:18 -0700
From:   Jonathan Corbet <corbet@....net>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
        Simon Horman <horms+renesas@...ge.net.au>,
        Yoshinori Sato <ysato@...rs.sourceforge.jp>,
        Rich Felker <dalias@...c.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Kate Stewart <kstewart@...uxfoundation.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [patch 0/2] LICENSES: Fix fallout from recent SPDX conversions

On Wed, 16 Jan 2019 11:26:51 +0100
Thomas Gleixner <tglx@...utronix.de> wrote:

> Recent SPDX conversions introduced new wreckage:
> 
>  arch/sh/lib/ashiftrt.S: 1:42 Invalid Exception ID: GCC-exception-2.0
>  ...
>  arch/sh/include/mach-ecovec24/mach/partner-jet-setup.txt: 1:38 Invalid token: "
>  ,,,
> 
> The first group is due to using an exception identifier without adding the
> exception text to the LICENSES directory.
> 
> The second one is due to the magic conment format in the SuperH bootcode
> files.
> 
> At least the first one could have been caught by checkpatch.pl:
> 
> WARNING: 'SPDX-License-Identifier: GPL-2.0+ WITH GCC-exception-2.0' is not supported in LICENSES/...
> #38: FILE: arch/sh/lib/ashiftrt.S:1:
> +/* SPDX-License-Identifier: GPL-2.0+ WITH GCC-exception-2.0
> 
> ....
> 
> The following series addresses both issues.

I've applied both to the docs tree, thanks.

jon