From: Jonathan Corbet <corbet@lwn.net>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Simon Horman <horms+renesas@verge.net.au>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
Andrew Morton <akpm@linux-foundation.org>,
Kate Stewart <kstewart@linuxfoundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [patch 0/2] LICENSES: Fix fallout from recent SPDX conversions
Date: Wed, 16 Jan 2019 14:56:18 -0700 [thread overview]
Message-ID: <20190116145618.6b8e8a81@lwn.net> (raw)
In-Reply-To: <20190116102651.489113812@linutronix.de>
On Wed, 16 Jan 2019 11:26:51 +0100
Thomas Gleixner <tglx@linutronix.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
prev parent reply other threads:[~2019-01-16 21:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 10:26 [patch 0/2] LICENSES: Fix fallout from recent SPDX conversions Thomas Gleixner
2019-01-16 10:26 ` [patch 1/2] LICENSES: Add GCC runtime library exception text Thomas Gleixner
2019-01-16 15:36 ` Greg Kroah-Hartman
2019-01-16 10:26 ` [patch 2/2] scripts/spdxcheck.py: Handle special quotation mark comments Thomas Gleixner
2019-01-16 15:38 ` Greg Kroah-Hartman
2019-01-20 15:32 ` [B.A.T.M.A.N.] " Sven Eckelmann
2019-01-20 15:32 ` Sven Eckelmann
2019-01-20 18:39 ` [B.A.T.M.A.N.] " Joe Perches
2019-01-20 18:39 ` Joe Perches
2019-02-06 18:50 ` [B.A.T.M.A.N.] " Sven Eckelmann
2019-02-06 18:50 ` Sven Eckelmann
2019-01-16 21:56 ` Jonathan Corbet [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190116145618.6b8e8a81@lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=dalias@libc.org \
--cc=gregkh@linuxfoundation.org \
--cc=horms+renesas@verge.net.au \
--cc=kstewart@linuxfoundation.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=ysato@users.sourceforge.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.