From: "Bradley M. Kuhn" <bkuhn@ebb.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-spdx@vger.kernel.org" <linux-spdx@vger.kernel.org>
Subject: Re: [PATCH v3] powerpc: Add missing SPDX license identifiers
Date: Tue, 25 Jan 2022 05:47:39 -0800 [thread overview]
Message-ID: <Ye//e3q46n57x/1l@ebb.org> (raw)
In-Reply-To: <YerO8MjbXlvbMEsZ@kroah.com>
> On Fri, Jan 21, 2022 at 03:13:50PM +0000, Christophe Leroy wrote:
> > Isn't it what GPL-2.0+ means ?
Greg Kroah-Hartman wrote:
> Yes, but look further down, as I point out below...
>
> > >> include/asm/epapr_hcalls.h:/* SPDX-License-Identifier: GPL-2.0+ OR BSD */
> > >> include/asm/fsl_hcalls.h:/* SPDX-License-Identifier: GPL-2.0+ OR BSD */
> > >> include/asm/ibmebus.h:/* SPDX-License-Identifier: GPL-2.0 OR OpenIB BSD */
> > >> include/asm/sfp-machine.h:/* SPDX-License-Identifier: LGPL-2.0+ */
> > >> kvm/mpic.c:// SPDX-License-Identifier: GPL-2.0
> > >> lib/crtsavres.S:/* SPDX-License-Identifier: GPL-2.0+ */
> > >> mm/book3s64/hash_4k.c:// SPDX-License-Identifier: LGPL-2.0
> > >> mm/book3s64/hash_64k.c:// SPDX-License-Identifier: LGPL-2.0
> > >> mm/book3s64/hash_hugepage.c:// SPDX-License-Identifier: LGPL-2.1
> > >> platforms/pseries/ibmebus.c:// SPDX-License-Identifier: GPL-2.0 OR OpenIB BSD
> > >> tools/head_check.sh:# SPDX-License-Identifier: GPL-2.0+
> > >> xmon/ppc.h:/* SPDX-License-Identifier: GPL-1.0+ */
If you're combining GPLv2-or-later works with LGPLv2.0/2.1 works, you'll have
to normalize to some GPLv2-based license (such as GPLv2-or-later), since
LGPLv2.1 requires that for combinations. You won't be able to carry along
the "OR 3-Clause-BSD" part once the combination is made. Similarly true with
GPLv2-or-later, but LGPL is the interesting one because it's explicit about
the need to change license notices to GPL notices when you combine.
-- bkuhn
next prev parent reply other threads:[~2022-01-25 14:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 11:03 [PATCH v3] powerpc: Add missing SPDX license identifiers Christophe Leroy
2022-01-21 14:35 ` Greg Kroah-Hartman
2022-01-21 15:13 ` Christophe Leroy
2022-01-21 15:19 ` Greg Kroah-Hartman
2022-01-21 15:34 ` Christophe Leroy
2022-01-21 16:00 ` Greg Kroah-Hartman
2022-01-21 18:15 ` Segher Boessenkool
2022-01-25 13:47 ` Bradley M. Kuhn [this message]
2022-01-21 14:36 ` Greg Kroah-Hartman
2022-01-21 18:09 ` Richard Fontana
2022-01-21 18:17 ` Richard Fontana
2022-01-22 5:20 ` J Lovejoy
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=Ye//e3q46n57x/1l@ebb.org \
--to=bkuhn@ebb.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).