From: Al Viro <viro@zeniv.linux.org.uk>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Qing Zhang <zhangqing@loongson.cn>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <maz@kernel.org>,
Huacai Chen <chenhuacai@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
linux-spdx@vger.kernel.org,
"open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
devicetree@vger.kernel.org, Ming Wang <wangming01@loongson.cn>
Subject: Re: Invalid License ID: GPL-3.0 for arch/mips/boot/dts/loongson/loongson64-2k1000.dtsi
Date: Tue, 20 Apr 2021 18:45:27 +0000 [thread overview]
Message-ID: <YH8hR5LkA9X5Eyfa@zeniv-ca.linux.org.uk> (raw)
In-Reply-To: <CAKXUXMyNf4xCF2mWr878MKDa0-8svaiR5GToQyoEVM4FbmfJ8w@mail.gmail.com>
On Tue, Apr 20, 2021 at 11:39:04AM +0200, Lukas Bulwahn wrote:
> Dear Qing,
>
> ./scripts/spdxcheck.py reports:
>
> arch/mips/boot/dts/loongson/loongson64-2k1000.dtsi: 1:28 Invalid
> License ID: GPL-3.0
>
> You have contributed this file with commit b1a792601f26 ("MIPS:
> Loongson64: DeviceTree for Loongson-2K1000") to the current
> linux-next.
>
> Do you intend to contribute this under this non-default license
> (GPL-3.0) for the kernel project or did you simply mean the default
> license GPL-2.0?
Ouch... That's quite likely to be impossible to distribute, since the
requirements of v2 and v3 are mutually incompatible and quite a bit of
the kernel is under v2-only, not v2-or-any-later-version.
Seriously, folks - talk to lawyers; if the result is *NOT* a mere aggregation
(i.e. is derived work wrt the kernel proper), you are in a copyright violation.
Moreover, if anything in that file is derived from others' work, you can't
use GPL-3.0 unless the terms for everything it's derived from allow
redistribution under GPL-3.0. Anything derived from others' GPL-2.0 work
(as opposed to GPL-2.0-or-later one) can't be relicensed to GPL-3.0 at
all.
prev parent reply other threads:[~2021-04-20 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 9:39 Lukas Bulwahn
2021-04-20 18:45 ` Al Viro [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=YH8hR5LkA9X5Eyfa@zeniv-ca.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=chenhuacai@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=maz@kernel.org \
--cc=tglx@linutronix.de \
--cc=tsbogend@alpha.franken.de \
--cc=wangming01@loongson.cn \
--cc=zhangqing@loongson.cn \
/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
all inboxes | Powered by JetHome®