Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Tue, 25 Jan 2022 05:47:39 -0800
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
Message-ID: <Ye//e3q46n57x/1l@ebb.org>
References: <d2c52284244d6dcb3472d2041abe43b456d116df.1642762977.git.christophe.leroy@csgroup.eu>
 <YerEuE6XlslE3Goo@kroah.com>
 <24829c2f-6855-c8d6-7ae4-17c5517f890d@csgroup.eu>
 <YerO8MjbXlvbMEsZ@kroah.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <YerO8MjbXlvbMEsZ@kroah.com>
Precedence: bulk

> 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