From: Joe Perches <joe@perches.com>
To: Miko Larsson <mikoxyzzz@gmail.com>,
minchan@kernel.org, ngupta@vflare.org, senozhatsky@chromium.org,
axboe@kernel.dk, linux-kernel@vger.kernel.org,
linux-block@vger.kernel.org
Cc: hch@infradead.org
Subject: Re: [PATCH v2 1/2] zram: zram_drv: add SPDX license identifiers
Date: Fri, 24 Dec 2021 08:33:13 -0800 [thread overview]
Message-ID: <bc5b21934b2b871d2745dab8f469ce6458222594.camel@perches.com> (raw)
In-Reply-To: <985cf51402ff6ea2c199869c3501a43a6588ae4f.camel@gmail.com>
(resending, original sent with an html part, unknown how)
On Fri, 2021-12-24 at 14:13 +0100, Miko Larsson wrote:
> On Tue, 2021-12-21 at 01:33 -0800, Joe Perches wrote:
> > GPL v2 is a permissive license and this SPDX tag should probably be
> >
> > // SPDX-License-Identifier: GPL-2.0-or-later or BSD-3-Clause
>
> It shouldn't be GPL-2.0-or-later, because the original copyright notice
> doesn't have an "or later" clause.
On its face, a GPL-2.0 license notice grant does _not_ need to
include any 'or later' content.
The GPL 2.0 license is permissive, it's at the _grantee's_ option.
I believe Nitin Gupta, the original author and submitter, should
declare whether or not he intended the license to include the
'or later' option.
Nitin?
Did you intend to use GPL-2.0 only and exclude GPL-3.0 or any later
version?
next prev parent reply other threads:[~2021-12-24 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 6:32 [PATCH v2 0/2] Fix some formatting problems Miko Larsson
2021-12-17 6:32 ` [PATCH v2 1/2] zram: zram_drv: add SPDX license identifiers Miko Larsson
2021-12-21 8:58 ` Christoph Hellwig
2021-12-21 9:33 ` Joe Perches
2021-12-24 13:13 ` Miko Larsson
2021-12-24 16:33 ` Joe Perches [this message]
2021-12-17 6:32 ` [PATCH v2 2/2] zram: zram_drv: replace 'strlcpy()' Miko Larsson
2021-12-21 8:59 ` Christoph Hellwig
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=bc5b21934b2b871d2745dab8f469ce6458222594.camel@perches.com \
--to=joe@perches.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikoxyzzz@gmail.com \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=senozhatsky@chromium.org \
/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