From: Joe Perches <joe@perches.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.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 01:14:25 -0700 [thread overview]
Message-ID: <77d0d8ff4cb9984ac20546842292aafd9e3b2e25.camel@perches.com> (raw)
In-Reply-To: <20180518075227.GF6828@piout.net>
On Fri, 2018-05-18 at 09:52 +0200, Alexandre Belloni wrote:
> On 17/05/2018 18:13:25-0700, Joe Perches wrote:
> > On Thu, 2018-05-17 at 21:39 +0200, Alexandre Belloni wrote:
> > > 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.
> >
> > Just because you submitted it does not mean you
> > are the copyright holder.
> >
> > > > > 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
> >
> > How do you know that?
> >
>
> The fact is that it should have been submitted with the SPDX identifier
> to be consistent with the rest of the driver. If you can't trust me on
> that, then, you can't probably trust anyone submitting anything new
> driver to the kernel.
Silly.
> I still don't understand why you are making an issue out of this.
Correctness in licensing text is important.
> Because my email address doesn't match the copyright holder's name
> doesn't mean I'm not allowed to fix my own mistake.
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.
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.
cheers, Joe
next prev parent reply other threads:[~2018-05-18 8:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 19:23 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 [this message]
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=77d0d8ff4cb9984ac20546842292aafd9e3b2e25.camel@perches.com \
--to=joe@perches.com \
--cc=Allan.Nielsen@microsemi.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.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
all inboxes | Powered by JetHome®