From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [patch 1/2] LICENSES: Add GCC runtime library exception text
Date: Wed, 16 Jan 2019 16:36:28 +0100 [thread overview]
Message-ID: <20190116153628.GA871@kroah.com> (raw)
In-Reply-To: <20190116104127.590053479@linutronix.de>
On Wed, Jan 16, 2019 at 11:26:52AM +0100, Thomas Gleixner wrote:
> A recent commit added SPDX identifiers to the SuperH low level library code
> which originates from GCC. This code is licensed under the GPL 2.0 or later
> with the GCC runtime library exception.
>
> Unfortunately the authors did not bother to add the exception text to the
> LICENSES directory so spdxcheck fails with:
>
> arch/sh/lib/ashiftrt.S: 1:42 Invalid Exception ID: GCC-exception-2.0
> arch/sh/lib/ashlsi3.S: 1:42 Invalid Exception ID: GCC-exception-2.0
> arch/sh/lib/ashrsi3.S: 1:42 Invalid Exception ID: GCC-exception-2.0
> arch/sh/lib/lshrsi3.S: 1:42 Invalid Exception ID: GCC-exception-2.0
> arch/sh/lib/movmem.S: 1:42 Invalid Exception ID: GCC-exception-2.0
> arch/sh/lib/udiv_qrnnd.S: 1:42 Invalid Exception ID: GCC-exception-2.0
> arch/sh/lib/udivsi3.S: 1:42 Invalid Exception ID: GCC-exception-2.0
> arch/sh/lib/udivsi3_i4i-Os.S: 1:42 Invalid Exception ID: GCC-exception-2.0
> arch/sh/lib/udivsi3_i4i.S: 1:42 Invalid Exception ID: GCC-exception-2.0
>
> Add the exception text along with the required tags which allow automated
> checking.
>
> Fixes: 4494ce4fb4ff ("sh: lib: convert to SPDX identifiers")
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> Cc: Simon Horman <horms+renesas@verge.net.au>
> Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
> Cc: Rich Felker <dalias@libc.org>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Kate Stewart <kstewart@linuxfoundation.org>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> ---
> LICENSES/exceptions/GCC-exception-2.0 | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2019-01-16 15:36 UTC|newest]
Thread overview: 9+ 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 [this message]
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 ` Sven Eckelmann
2019-01-20 18:39 ` Joe Perches
2019-02-06 18:50 ` Sven Eckelmann
2019-01-16 21:56 ` [patch 0/2] LICENSES: Fix fallout from recent SPDX conversions Jonathan Corbet
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=20190116153628.GA871@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=dalias@libc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox