All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Kate Stewart <kstewart@linuxfoundation.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Ondrej Mosnacek <omosnacek@gmail.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
	<linux-crypto@vger.kernel.org>
Subject: Re: [patch 3/9] crypto: morus - Cleanup license mess
Date: Fri, 18 Jan 2019 07:50:58 +0100	[thread overview]
Message-ID: <20190118065058.GA9727@kroah.com> (raw)
In-Reply-To: <CAOMZO5CsTiQV78d6ZvUBwzzU9iF8ZnCpp_O7VBrvxstZ6kNNRg@mail.gmail.com>

On Thu, Jan 17, 2019 at 10:26:07PM -0200, Fabio Estevam wrote:
> On Thu, Jan 17, 2019 at 9:17 PM Thomas Gleixner <tglx@linutronix.de> wrote:
> 
> > --- a/include/crypto/morus1280_glue.h
> > +++ b/include/crypto/morus1280_glue.h
> > @@ -1,15 +1,10 @@
> > -/* SPDX-License-Identifier: GPL-2.0 */
> > +/* SPDX-License-Identifier: GPL-2.0-or-later */
> 
> Shouldn't this be: /* SPDX-License-Identifier: GPL-2.0+ */ ?
> 
> At least this is the form documented in Documentation/process/license-rules.rst:
> 
> " License identifiers for licenses like [L]GPL with the 'or later' option
>    are constructed by using a "+" for indicating the 'or later' option.::
> 
>       // SPDX-License-Identifier: GPL-2.0+"

Either works, please see LICENSES/preferred/GPL-2.0

Personally, I think we should stick with the "+" version as that is the
much more prevalent use in the kernel at the moment, but it's Thomas's
call, not mine.

thanks,

greg k-h

  reply	other threads:[~2019-01-18  6:51 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17 23:14 [patch 0/9] treewide: Cleanup recently added license mess Thomas Gleixner
2019-01-17 23:14 ` [patch 1/9] block: Cleanup license notice Thomas Gleixner
2019-01-18  2:53   ` Bart Van Assche
2019-01-18  4:21   ` Jens Axboe
2019-01-17 23:14 ` [patch 2/9] crypto: aegis - Cleanup license mess Thomas Gleixner
2019-01-18  8:02   ` Ondrej Mosnáček
2019-01-25 10:47   ` Herbert Xu
2019-01-17 23:14 ` [patch 3/9] crypto: morus " Thomas Gleixner
2019-01-18  0:26   ` Fabio Estevam
2019-01-18  6:50     ` Greg Kroah-Hartman [this message]
2019-01-18  8:00   ` Ondrej Mosnáček
2019-01-17 23:14 ` [patch 4/9] crypto: aegis - Convert to SPDX license identifiers Thomas Gleixner
2019-01-18  8:01   ` Ondrej Mosnáček
2019-01-17 23:14 ` [patch 5/9] crypto: morus " Thomas Gleixner
2019-01-18  8:02   ` Ondrej Mosnáček
2019-01-17 23:14 ` [patch 6/9] ceph: quota: Cleanup license mess Thomas Gleixner
2019-01-18  9:42   ` Luis Henriques
2019-01-18  9:42     ` Luis Henriques
2019-01-18 10:48   ` Ilya Dryomov
2019-01-18 10:54     ` Thomas Gleixner
2019-01-17 23:14 ` [patch 7/9] smb3: " Thomas Gleixner
2019-01-19  5:43   ` Steve French
2019-01-17 23:14 ` [patch 8/9] tools: bpftool: " Thomas Gleixner
2019-01-17 23:24   ` Jakub Kicinski
2019-01-18  0:00     ` Thomas Gleixner
2019-01-18 23:28   ` Alexei Starovoitov
2019-01-17 23:14 ` [patch 9/9] vfio/pci: " Thomas Gleixner
2019-01-23 20:05   ` Alex Williamson

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=20190118065058.GA9727@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=festevam@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=omosnacek@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.