linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philippe Ombredanne <pombredanne@nexb.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>,
	Wolfgang Grandegger <wg@grandegger.com>,
	Marc Kleine-Budde <mkl@pengutronix.de>,
	"David S. Miller" <davem@davemloft.net>,
	linux-can@vger.kernel.org, netdev <netdev@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 05/11] can: rcar: use SPDX identifier for Renesas drivers
Date: Wed, 22 Aug 2018 20:16:45 +0200	[thread overview]
Message-ID: <CAOFm3uF9_rbELx0aYLDXpDnZfi2Z11V1Z4Ktw+DDJT62o2S1kQ@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5BiAyDMSR=2Y-4-1ftNuVtRS59sSJd_cdFmzX=0kgF0Bw@mail.gmail.com>

Hi Fabio,
On Wed, Aug 22, 2018 at 2:55 PM, Fabio Estevam <festevam@gmail.com> wrote:
> On Wed, Aug 22, 2018 at 3:30 AM, Wolfram Sang <wsa@the-dreams.de> wrote:
>>
>>> > +// SPDX-License-Identifier: GPL-2.0-or-later
>>>
>>> According to Documentation/process/license-rules.rst the format should
>>> be like this instead:
>>>
>>> // SPDX-License-Identifier: GPL-2.0+
>>
>> According to https://spdx.org/licenses/ it should be what I did above.
>
> Previous advice I saw was to follow the format described in
> Documentation/process/license-rules.rst
>
> Greg/Philippe,
>
> Any inputs on this matter?
>
> Thanks

IMHO we should always treat and use the
Documentation/process/license-rules.rst as the reference and not SPDX
proper who moves at its own pace and evolves its specs and license ids
independently of where we stand in the kernel.
If this is not right Doc patches are welcomed!
In this is very specific case this has been discussed on list a few
times. If I recall correctly Thomas also had an opinion on this...
So you are correct and this should be for now:
// SPDX-License-Identifier: GPL-2.0+

-- 
Cordially
Philippe Ombredanne

  reply	other threads:[~2018-08-22 18:17 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-21 22:02 [PATCH 00/11] tree-wide: use SPDX identifier for Renesas drivers Wolfram Sang
2018-08-21 22:02 ` [PATCH 01/11] clk: renesas: " Wolfram Sang
2018-08-22  9:28   ` Simon Horman
2018-08-28  9:24   ` Geert Uytterhoeven
2018-08-28 20:51     ` Wolfram Sang
2018-08-31  1:19   ` Stephen Boyd
2018-08-21 22:02 ` [PATCH 02/11] dmaengine: " Wolfram Sang
2018-08-22  0:42   ` Kuninori Morimoto
2018-08-22  6:32     ` Wolfram Sang
2018-08-21 22:02 ` [PATCH 03/11] i2c: " Wolfram Sang
2018-08-22  9:34   ` Simon Horman
2018-08-21 22:02 ` [PATCH 04/11] mmc: " Wolfram Sang
2018-08-22  9:34   ` Simon Horman
2018-08-22  9:49   ` Ulf Hansson
2018-08-21 22:02 ` [PATCH 05/11] can: rcar: " Wolfram Sang
2018-08-21 22:45   ` Fabio Estevam
2018-08-22  6:30     ` Wolfram Sang
2018-08-22 12:55       ` Fabio Estevam
2018-08-22 18:16         ` Philippe Ombredanne [this message]
2018-08-22 19:31           ` Greg Kroah-Hartman
2018-08-22 19:36             ` Wolfram Sang
2018-08-21 22:02 ` [PATCH 06/11] net: ethernet: renesas: " Wolfram Sang
2018-08-22  8:56   ` Sergei Shtylyov
2018-08-22  9:36   ` Simon Horman
2018-08-23  4:38   ` David Miller
2018-08-21 22:02 ` [PATCH 07/11] phy: " Wolfram Sang
2018-08-22  5:57   ` Yoshihiro Shimoda
2018-08-22  9:35   ` Simon Horman
2018-08-21 22:02 ` [PATCH 08/11] pwm: " Wolfram Sang
2018-08-22  9:33   ` Simon Horman
2018-08-21 22:02 ` [PATCH 09/11] soc: renesas: " Wolfram Sang
2018-08-22  9:32   ` Simon Horman
2018-08-21 22:02 ` [PATCH 10/11] spi: " Wolfram Sang
2018-08-22  9:33   ` Simon Horman
2018-08-28 20:59   ` Applied "spi: use SPDX identifier for Renesas drivers" to the spi tree Mark Brown
2018-08-21 22:02 ` [PATCH 11/11] watchdog: use SPDX identifier for Renesas drivers Wolfram Sang
2018-08-21 23:58   ` Guenter Roeck
2018-08-22  9:35   ` Simon Horman

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=CAOFm3uF9_rbELx0aYLDXpDnZfi2Z11V1Z4Ktw+DDJT62o2S1kQ@mail.gmail.com \
    --to=pombredanne@nexb.com \
    --cc=davem@davemloft.net \
    --cc=festevam@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kuninori.morimoto.gx@gmail.com \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=wg@grandegger.com \
    --cc=wsa+renesas@sang-engineering.com \
    --cc=wsa@the-dreams.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 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).