All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-mtd@lists.infradead.org,
	Boris Brezillon <boris.brezillon@bootlin.com>,
	Dinh Nguyen <dinguyen@kernel.org>,
	linux-kernel@vger.kernel.org, Marek Vasut <marek.vasut@gmail.com>,
	Brian Norris <computersforpeace@gmail.com>,
	Richard Weinberger <richard@nod.at>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] mtd: nand: denali: use SPDX-License-Identifier and fix license mismatch
Date: Tue, 4 Sep 2018 23:56:51 +0200	[thread overview]
Message-ID: <20180904235651.12708e91@xps13> (raw)
In-Reply-To: <1534735596-10876-1-git-send-email-yamada.masahiro@socionext.com>

Hi Masahiro,

Masahiro Yamada <yamada.masahiro@socionext.com> wrote on Mon, 20 Aug
2018 12:26:36 +0900:

> Use SPDX-License-Identifier instead of the license boilerplates.
> 
> This conversion makes it easier for us to scan the license, then
> I notice license mismatch problems.
> 
> The license blocks in denali* indicate GPL-2.0 "only", while the
> MODULE_LICENSE in denali.c and denali_dt.c is GPL-2.0 "or later"
> as explained in include/linux/module.h as follows:
> 
>   "GPL"                           [GNU Public License v2 or later]
>   "GPL v2"                        [GNU Public License v2]
> 
> I fixed the MODULE_LICENSE tags, assuming the license blocks are
> the authors' intention.
> 
> Also, add missing MODULE_DESCRIPTION/AUTHOR to denali.c
> 
> While I am touching the license things, I added my credit to denali.c
> because this driver was largely re-written by me in 2017.
> 
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---

Applied to nand/next with subject prefix s/nand/rawnand/.

Thanks,
Miquèl

      reply	other threads:[~2018-09-04 21:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-20  3:26 [PATCH] mtd: nand: denali: use SPDX-License-Identifier and fix license mismatch Masahiro Yamada
2018-09-04 21:56 ` Miquel Raynal [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=20180904235651.12708e91@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=boris.brezillon@bootlin.com \
    --cc=computersforpeace@gmail.com \
    --cc=dinguyen@kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marek.vasut@gmail.com \
    --cc=richard@nod.at \
    --cc=yamada.masahiro@socionext.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.