All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jules Irenge <jbi.octave@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [PATCH 1/2] staging: mt7621-dma: add SPDX GPL-2.0 or later version license identifier
Date: Fri, 1 Mar 2019 16:39:35 +0100	[thread overview]
Message-ID: <20190301153935.GA3877@kroah.com> (raw)
In-Reply-To: <20190301151801.7886-2-jbi.octave@gmail.com>

On Fri, Mar 01, 2019 at 03:18:00PM +0000, Jules Irenge wrote:
> Add SPDX GPL-2.0-or-later license to fix missing SPDX warning
>  reported by checkpatch.pl.
> 
> Signed-off-by: Jules Irenge <jbi.octave@gmail.com>
> ---
>  drivers/staging/mt7621-dma/mtk-hsdma.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/staging/mt7621-dma/mtk-hsdma.c b/drivers/staging/mt7621-dma/mtk-hsdma.c
> index d67a2504adb1..7d69586f23c0 100644
> --- a/drivers/staging/mt7621-dma/mtk-hsdma.c
> +++ b/drivers/staging/mt7621-dma/mtk-hsdma.c
> @@ -1,3 +1,4 @@
> +// SPDX-License-Identifier: GPL-2.0-or-later

Shouldn't this be:

// SPDX-License-Identifier: GPL-2.0+

The "or later" is starting to get used, but I don't think it's all that
prelevant yet.  What did you read to decide to use that format instead
of the "+" format?

thanks,

greg k-h


  reply	other threads:[~2019-03-01 15:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-01 15:17 [PATCH 0/2] staging: mt7621-dma: SPDX license cleanups Jules Irenge
2019-03-01 15:18 ` [PATCH 1/2] staging: mt7621-dma: add SPDX GPL-2.0 or later version license identifier Jules Irenge
2019-03-01 15:39   ` Greg KH [this message]
2019-03-01 17:38     ` Jules Octave
2019-03-01 20:01       ` Greg KH
2019-03-02  0:15         ` [Outreachy kernel] " Jules Octave
2019-03-02  6:30           ` Julia Lawall
2019-03-02  7:29             ` Jules Octave
2019-03-02  7:36               ` Julia Lawall
2019-03-01 15:18 ` [PATCH 2/2] staging: mt7621-dma: remove license boilerplate text Jules Irenge

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=20190301153935.GA3877@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jbi.octave@gmail.com \
    --cc=outreachy-kernel@googlegroups.com \
    /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.