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+ license identifier
Date: Sat, 2 Mar 2019 08:45:44 +0100 [thread overview]
Message-ID: <20190302074544.GA16379@kroah.com> (raw)
In-Reply-To: <20190302001115.20477-2-jbi.octave@gmail.com>
On Sat, Mar 02, 2019 at 12:11:14AM +0000, Jules Irenge wrote:
> Add SPDX GPL-2.0+ 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
Are you sure you changed the identifer to match what said above in your
changelog? :(
next prev parent reply other threads:[~2019-03-02 7:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-02 0:11 [PATCH 0/2] staging: mt7621-dma: SPDX license cleanups Jules Irenge
2019-03-02 0:11 ` [PATCH 1/2] staging: mt7621-dma: add SPDX GPL-2.0+ license identifier Jules Irenge
2019-03-02 7:45 ` Greg KH [this message]
2019-03-02 10:42 ` Jules Octave
2019-03-02 0:11 ` [PATCH 2/2] staging: mt7621-dma: Remove license boilerplate text Jules Irenge
2019-03-02 6:32 ` [Outreachy kernel] " Julia Lawall
2019-03-02 7:37 ` Jules Octave
[not found] ` <alpine.DEB.2.21.1903020906590.2572@hadrien>
2019-03-02 8:48 ` Jules Octave
2019-03-02 6:33 ` [Outreachy kernel] [PATCH 0/2] staging: mt7621-dma: SPDX license cleanups Julia Lawall
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=20190302074544.GA16379@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.