From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: rawnand: sh_flctl: convert to SPDX identifiers
Date: Thu, 8 Nov 2018 11:13:00 +0100 [thread overview]
Message-ID: <20181108111300.1f9d4457@bbrezillon> (raw)
In-Reply-To: <20181108095728.6c19b8f0@bbrezillon>
On Thu, 8 Nov 2018 09:57:28 +0100
Boris Brezillon <boris.brezillon@bootlin.com> wrote:
> On Thu, 8 Nov 2018 06:39:20 +0000
> Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> wrote:
>
> > From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> >
> > This patch updates license to use SPDX-License-Identifier
> > instead of verbose license text.
> >
> > As original license mentioned, it is GPL-2.0 in SPDX.
> > Then, MODULE_LICENSE() should be "GPL v2" instead of "GPL".
> > See ${LINUX}/include/linux/module.h
> >
> > "GPL" [GNU Public License v2 or later]
> > "GPL v2" [GNU Public License v2]
>
> I had a similar case recently and I based my SPDX tag on the
> MODULE_LICENSE() value instead of the license header.
> Is this "license header" > MODULE_LICENSE() rule documented
> somewhere?
Looks like you made the right choice [1]. I'll fix my patches to follow
this rule.
[1]https://lore.kernel.org/linux-rtc/20180625015832.GB30408@kroah.com/
next prev parent reply other threads:[~2018-11-08 10:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 6:39 [PATCH] mtd: rawnand: sh_flctl: convert to SPDX identifiers Kuninori Morimoto
2018-11-08 8:57 ` Boris Brezillon
2018-11-08 10:13 ` Boris Brezillon [this message]
2018-11-09 0:15 ` Kuninori Morimoto
2018-11-18 20:47 ` Miquel Raynal
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=20181108111300.1f9d4457@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=miquel.raynal@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).