public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Joe Perches <joe@perches.com>
Cc: "David S . Miller" <davem@davemloft.net>,
	Allan Nielsen <Allan.Nielsen@microsemi.com>,
	razvan.stefanescu@nxp.com, po.liu@nxp.com,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Andrew Lunn <andrew@lunn.ch>,
	Florian Fainelli <f.fainelli@gmail.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next ] net: mscc: Add SPDX identifier
Date: Thu, 17 May 2018 21:39:00 +0200	[thread overview]
Message-ID: <20180517193900.GE6828@piout.net> (raw)
In-Reply-To: <53ccb8c58e4c3e224ba694c0628096d0c041ba1a.camel@perches.com>

On 17/05/2018 12:28:59-0700, Joe Perches wrote:
> On Thu, 2018-05-17 at 21:23 +0200, Alexandre Belloni wrote:
> > ocelot_qsys.h is missing the SPDX identfier, fix that.
> > 
> > Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
> 
> Only the copyright holders should ideally be modifying
> these and also removing other license content.
> 
> For instance, what's the real intent here?
> 

Well, if you have a look, I submitted that file this cycle and it is the
only one that doesn't have the proper SPDX identifier. This is a mistake
I'm fixing.

> > diff --git a/drivers/net/ethernet/mscc/ocelot_qsys.h b/drivers/net/ethernet/mscc/ocelot_qsys.h
> []
> > @@ -1,7 +1,7 @@
> > +/* SPDX-License-Identifier: (GPL-2.0 OR MIT) */
> 
> GPL 2.0+ or 2.0?
> 

2.0


-- 
Alexandre Belloni, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-05-17 19:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-17 19:23 [PATCH net-next ] net: mscc: Add SPDX identifier Alexandre Belloni
2018-05-17 19:28 ` Joe Perches
2018-05-17 19:39   ` Alexandre Belloni [this message]
2018-05-18  1:13     ` Joe Perches
2018-05-18  7:52       ` Alexandre Belloni
2018-05-18  8:14         ` Joe Perches
2018-05-18  8:20           ` Alexandre Belloni
2018-05-18  8:38 ` Allan W. Nielsen
2018-05-18 15:30 ` David Miller

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=20180517193900.GE6828@piout.net \
    --to=alexandre.belloni@bootlin.com \
    --cc=Allan.Nielsen@microsemi.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=po.liu@nxp.com \
    --cc=razvan.stefanescu@nxp.com \
    --cc=thomas.petazzoni@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