From: "Opensource [Steve Twiss]" <stwiss.opensource@diasemi.com>
To: Paul Bolle <pebolle@tiscali.nl>,
"Opensource [Steve Twiss]" <stwiss.opensource@diasemi.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
Samuel Ortiz <sameo@linux.intel.com>,
DT <devicetree@vger.kernel.org>,
David Dajun Chen <david.chen@diasemi.com>,
INPUT <linux-input@vger.kernel.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
LKML <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"Pawel Moll" <pawel.moll@arm.com>,
Rob Herring <robh+dt@kernel.org>,
"Support Opensource" <Support.Opensource@diasemi.com>
Subject: RE: [RESEND PATCH V2 1/2] input: misc: da9063: OnKey driver
Date: Fri, 24 Apr 2015 13:45:55 +0000 [thread overview]
Message-ID: <6ED8E3B22081A4459DAC7699F3695FB7014B217581@SW-EX-MBX02.diasemi.com> (raw)
In-Reply-To: <1429343726.16771.129.camel@x220>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1140 bytes --]
On 18 April 2015 08:55 Paul Bolle wrote:
> There's still a license mismatch left (it probably got lost in the noise
> when I finally noticed that the header comment mentioned the LGPL in
> V1).
>
> On Fri, 2015-04-17 at 13:03 +0100, S Twiss wrote:
> > + * as published by the Free Software Foundation; either version 2
> > + * of the License, or (at your option) any later version.
>
> This states the license is GPL v2 or later.
>
> > +MODULE_LICENSE("GPL v2");
>
> And, according to include/linux/module.h, this states the license is
> just GPL v2. So I think either the license comment or the license ident
> used in the MODULE_LICENSE() macro needs to change.
>
Got it. Thanks for your comments.
I have altered the MODULE_LICENSE() to be "GPL" instead of "GPL v2".
That should fix it.
That seems to be a fairly common mistake in the kernel. When I did a
straw-poll, around 10% of files came up with "GPL v2" and contained
"any later version" text.
Regards,
Steve.
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2015-04-24 13:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 12:03 [RESEND PATCH V2 0/2] Add OnKey support for DA9063 S Twiss
2015-04-17 12:03 ` [RESEND PATCH V2 2/2] devicetree: Add bindings for DA9063 OnKey S Twiss
2015-04-17 12:03 ` [RESEND PATCH V2 1/2] input: misc: da9063: OnKey driver S Twiss
2015-04-17 16:15 ` Dmitry Torokhov
2015-04-24 13:36 ` Opensource [Steve Twiss]
2015-04-29 16:00 ` Opensource [Steve Twiss]
2015-04-18 7:55 ` Paul Bolle
2015-04-24 13:45 ` Opensource [Steve Twiss] [this message]
2015-04-24 16:53 ` Paul Bolle
2015-04-28 11:56 ` Lee Jones
2015-04-29 16:01 ` Opensource [Steve Twiss]
2015-04-29 16:15 ` Lee Jones
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=6ED8E3B22081A4459DAC7699F3695FB7014B217581@SW-EX-MBX02.diasemi.com \
--to=stwiss.opensource@diasemi.com \
--cc=Support.Opensource@diasemi.com \
--cc=david.chen@diasemi.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=pebolle@tiscali.nl \
--cc=robh+dt@kernel.org \
--cc=sameo@linux.intel.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;
as well as URLs for NNTP newsgroup(s).