From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] power: reset: qnap-poweroff: Fix License String
Date: Mon, 21 Jan 2013 09:11:29 +0100 [thread overview]
Message-ID: <20130121081129.GP8668@pengutronix.de> (raw)
In-Reply-To: <20130120204728.GA16339@lizard.gateway.2wire.net>
Hello Anton,
On Sun, Jan 20, 2013 at 12:47:29PM -0800, Anton Vorontsov wrote:
> On Sun, Jan 20, 2013 at 09:13:36PM +0100, Uwe Kleine-K?nig wrote:
> > On Tue, Jan 08, 2013 at 07:15:26PM +0100, Andrew Lunn wrote:
> > > GPLv2+ is not a valid license string. Replace it with one that is.
> > >
> > > Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> > > ---
> > > drivers/power/reset/qnap-poweroff.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/power/reset/qnap-poweroff.c b/drivers/power/reset/qnap-poweroff.c
> > > index ca0b476..8af772b 100644
> > > --- a/drivers/power/reset/qnap-poweroff.c
> > > +++ b/drivers/power/reset/qnap-poweroff.c
> > > @@ -121,4 +121,4 @@ module_platform_driver(qnap_power_off_driver);
> > >
> > > MODULE_AUTHOR("Andrew Lunn <andrew@lunn.ch>");
> > > MODULE_DESCRIPTION("QNAP Power off driver");
> > > -MODULE_LICENSE("GPLv2+");
> > > +MODULE_LICENSE("GPL v2");
> > This change is wrong.
> >
> > According to include/linux/module.h "GPL v2" means exactly that: version
> > 2. As the file specifies v2 or later in the header you have to use "GPL"
> > which means v2 or later.
>
> Does it even make sense to have the two separate things ("GPL v2" and
> "GPL")?
Yeah. If you had another OS project that uses GPL-4 you can just copy
over a GPL-2+ driver to it, not an GPL-2 driver. So assuming the kernel
will stay at GPL-2 forever it doesn't make any difference for the
kernel. But other projects might benefit. (And if in the future someone
might want to change the kernel to GPL-4, she only needs to contact the
GPL-2 authors and can legally change GPL-2+ to GPL-4+.)
> Suppose there is a global change that modifies a bunch of drivers, some of
> them are GPLv2+. Now, the author of the global change is submitting it
> under "GPL v2 only" license, which, by definition, turns any GPLv2+ code
> into "GPL v2 only", right?
See http://yarchive.net/comp/linux/dual_license_bsd_gpl.html for Linus'
POV. It's an old mail, but I think it still applies.
> So, changing from GPLv2+ to "GPL v2 only" is OK, but not the other way
> around.
OK as in (probably) legal. OK as in fair is questionable.
> IANAL, tho.
ditto.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2013-01-21 8:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 12:25 [PATCH 0/4] Power off drivers for QNAP and LSXL Andrew Lunn
2012-12-28 12:25 ` [PATCH 1/4] Power: Reset: Driver to turn QNAP board power off Andrew Lunn
2013-01-06 21:55 ` Anton Vorontsov
2013-01-08 18:15 ` [PATCH] power: reset: qnap-poweroff: Fix License String Andrew Lunn
2013-01-20 2:05 ` Anton Vorontsov
2013-01-20 20:13 ` Uwe Kleine-König
2013-01-20 20:47 ` Anton Vorontsov
2013-01-21 8:11 ` Uwe Kleine-König [this message]
2012-12-28 12:25 ` [PATCH 2/4] ARM: Kirkwood: Make use of the QNAP Power off driver Andrew Lunn
2012-12-28 12:25 ` [PATCH 3/4] Power: Reset: Power off by restarting Andrew Lunn
2012-12-28 18:59 ` Michael Walle
2013-01-06 22:04 ` Anton Vorontsov
2013-01-07 6:42 ` Andrew Lunn
2013-01-07 7:00 ` Anton Vorontsov
2013-01-07 11:27 ` Jason Cooper
2013-01-31 18:54 ` [PATCH] power/reset: restart: remove __dev{init,exit} Jason Cooper
2013-01-31 18:57 ` Jason Cooper
2013-01-31 20:02 ` Andrew Lunn
2013-01-31 20:20 ` Jason Cooper
2013-02-03 3:43 ` Anton Vorontsov
2012-12-28 12:25 ` [PATCH 4/4] ARM: Kirkwood: Convert LSXL to restart-poweroff driver Andrew Lunn
2012-12-28 19:16 ` Michael Walle
2012-12-28 19:39 ` Andrew Lunn
2012-12-28 23:11 ` Michael Walle
2013-01-23 12:53 ` [PATCH 0/4] Power off drivers for QNAP and LSXL Jason Cooper
2013-05-26 1:19 ` Jason Cooper
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=20130121081129.GP8668@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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).