From: Andrew Lunn <andrew@lunn.ch>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Michael Schmitz <schmitzmic@gmail.com>,
netdev@vger.kernel.org, fthain@telegraphics.com.au,
geert@linux-m68k.org, f.fainelli@gmail.com,
linux-m68k@vger.kernel.org, Michael.Karcher@fu-berlin.de,
LKML <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
Kate Stewart <kstewart@linuxfoundation.org>
Subject: Re: [v4,1/9] net-next: phy: new Asix Electronics PHY driver
Date: Sun, 20 Jan 2019 18:43:12 +0100 [thread overview]
Message-ID: <20190120174312.GC15048@lunn.ch> (raw)
In-Reply-To: <alpine.DEB.2.21.1901181121101.1647@nanos.tec.linutronix.de>
On Fri, Jan 18, 2019 at 11:22:39AM +0100, Thomas Gleixner wrote:
> Michael,
>
> On Thu, 19 Apr 2018, Michael Schmitz wrote:
>
> > --- /dev/null
> > +++ b/drivers/net/phy/asix.c
> > @@ -0,0 +1,63 @@
> > +// SPDX-License-Identifier: GPL-2.0
> > +/* Driver for Asix PHYs
> > + *
> > + * Author: Michael Schmitz <schmitzmic@gmail.com>
> > + *
> > + * This program is free software; you can redistribute it and/or modify it
> > + * under the terms of the GNU General Public License as published by the
> > + * Free Software Foundation; either version 2 of the License, or (at your
> > + * option) any later version.
> > + *
> > + */
>
> This license information is broken. The SPDX license identifier and the
> boiler plate text are contradicting. The SPDX id is GPL v2 only and the
> boiler plate says v2 or later.
Hi Thomas
Please see:
https://www.spinics.net/lists/netdev/msg544312.html
The first two patches are simple SPDX converstions. Then it gets
interesting trying to sort out license inconsistencies.
Andrew
next prev parent reply other threads:[~2019-01-20 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1524103526-12240-2-git-send-email-schmitzmic@gmail.com>
2019-01-18 10:22 ` [v4,1/9] net-next: phy: new Asix Electronics PHY driver Thomas Gleixner
2019-01-20 17:43 ` Andrew Lunn [this message]
2019-01-20 22:44 ` Michael Schmitz
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=20190120174312.GC15048@lunn.ch \
--to=andrew@lunn.ch \
--cc=Michael.Karcher@fu-berlin.de \
--cc=f.fainelli@gmail.com \
--cc=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=schmitzmic@gmail.com \
--cc=tglx@linutronix.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