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: Fri, 18 May 2018 10:20:58 +0200	[thread overview]
Message-ID: <20180518082058.GG6828@piout.net> (raw)
In-Reply-To: <77d0d8ff4cb9984ac20546842292aafd9e3b2e25.camel@perches.com>

On 18/05/2018 01:14:25-0700, Joe Perches wrote:
> Mostly, it's a question of what the original
> license is.  As far as I can tell, microsemi
> publishes their code only under an MIT license.
> 

This code didn't exist until I wrote it. The original license is the one
from the SPDX identifier.

> The MIT license does allow sublicensing, so
> it does seem you can choose what additional
> license restrictions you can assert as long
> as the original MIT license is also followed.
> 

Then all is good.


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

  reply	other threads:[~2018-05-18  8:51 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
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 [this message]
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=20180518082058.GG6828@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