From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: "Sébastien Szymanski" <sebastien.szymanski@armadeus.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
"Rob Herring" <robh+dt@kernel.org>,
"Pawel Moll" <pawel.moll@arm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
devicetree@vger.kernel.org, "Kumar Gala" <galak@codeaurora.org>
Subject: Re: [PATCH 1/2] Input: add support for Semtech SX8654 I2C touchscreen controller
Date: Sat, 07 Mar 2015 14:26:45 -0800 [thread overview]
Message-ID: <FACD03DB-5CFC-4C18-A185-1031903E3AAE@gmail.com> (raw)
In-Reply-To: <1425766340.2300.29.camel@x220>
On March 7, 2015 2:12:20 PM PST, Paul Bolle <pebolle@tiscali.nl> wrote:
>On Sat, 2015-03-07 at 14:02 -0800, Dmitry Torokhov wrote:
>> On March 7, 2015 1:54:41 PM PST, Paul Bolle <pebolle@tiscali.nl>
>wrote:
>> >By that logic we might as well simplify the logic of
>> >license_is_gpl_compatible() and MODULE_LICENSE() quite a bit. Why
>check
>> >for six variants instead of just one and be done with it?
>>
>> Because nobody wants to go through hundreds of drivers and change
>them?
>
>Not fun, but surely doable.
>
>> >Anyhow, "GPL" and "GPL v2" are both allowed but not identical. So,
>> >unless a patch is applied to treat them interchangeably, somehow, in
>> >the module license checking code,
>>
>> They are treated interchangeably as far as I can see. Where do you
>see
>> "GPL" is being treated differently than "GPL v2".
>
>I'm not going to explain here why "GPL v2" or "GPL v2 or later" differ.
I was talking about them being treated differently from technological standpoint (i.e. the code), not from legal one.
>
>"GPL" is documented to mean "GPL v2 or later". "GPL v2" is documented
>to
>mean just that (see include/linux/module.h). Again, you're free to
>submit a patch to somehow simplify that. But unless a patch like that
>is
>applied, we should make sure MODULE_LICENSE() matches the actual
>license
>of the module involved.
If you want to fix up input drivers I'll take such patch, but I am sure more such cases will sneak in unless you also make sure that there are tools (such as checkpatch.pl) that can alert developers to the inconsistency.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2015-03-07 22:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 18:21 Sébastien Szymanski
2015-03-06 18:21 ` [PATCH 2/2] Input: sx8654 - add device tree bindings Sébastien Szymanski
2015-03-06 18:21 ` [PATCH 1/2] Input: add support for Semtech SX8654 I2C touchscreen controller Dmitry Torokhov
2015-03-07 0:57 ` Dmitry Torokhov
2015-03-07 12:32 ` Paul Bolle
2015-03-07 21:25 ` Dmitry Torokhov
2015-03-07 21:54 ` Paul Bolle
2015-03-07 22:02 ` Dmitry Torokhov
2015-03-07 22:12 ` Paul Bolle
2015-03-07 22:26 ` Dmitry Torokhov [this message]
2015-03-07 22:38 ` Paul Bolle
2015-03-08 4:51 ` Dmitry Torokhov
2015-03-11 10:56 ` MODULE_LICENSE(): "GPL" vs. "GPL v2" (Was: [PATCH 1/2] Input: add support for Semtech SX8654 I2C touchscreen controller) Paul Bolle
2015-03-12 0:41 ` Rusty Russell
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=FACD03DB-5CFC-4C18-A185-1031903E3AAE@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--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=sebastien.szymanski@armadeus.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®