From: Paul Bolle <pebolle@tiscali.nl>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
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 22:54:41 +0100 [thread overview]
Message-ID: <1425765281.2300.17.camel@x220> (raw)
In-Reply-To: <20150307212543.GA38770@dtor-ws>
On Sat, 2015-03-07 at 13:25 -0800, Dmitry Torokhov wrote:
> I am not sure if anyone cares about exact version of GPL in module
> information (2 only vs 2+) since it only used to figure out if the
> module taints kernel or not. In fact there are more modules that are v2
> only that claim GPL than the ones claiming GPL v2.
>
> dtor@dtor-ws:~/kernel/master$ for file in `grep -r -l 'MODULE_LICENSE("GPL")'`; do grep -H '2 as published' $file; done | wc -l
> 259
> dtor@dtor-ws:~/kernel/master$ for file in `grep -r -l 'MODULE_LICENSE("GPL v2")'`; do grep -H '2 as published' $file; do ne | wc -l
> 150
>
> Also:
>
> dtor@dtor-ws:~/kernel/master$ for file in `grep -r -l 'MODULE_LICENSE("GPL v2")'`; do grep -H '2 or ' $file; done | wc -l
> 68
> dtor@dtor-ws:~/kernel/master$ for file in `grep -r -l 'MODULE_LICENSE("GPL")'`; do grep -H '2 or ' $file; done | wc -l
> 237
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?
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, we ought to make each instance of
MODULE_LICENSE() match the actual license of the module it's used for.
Yes, that's annoying. You're free to submit a patch to end all the
busywork this brings along. But I fear there's a reason for all that
busywork. Please prove me wrong. It would make everyone's life a bit
easier.
Paul Bolle
next prev parent reply other threads:[~2015-03-07 21:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 18:21 [PATCH 1/2] Input: add support for Semtech SX8654 I2C touchscreen controller Sébastien Szymanski
[not found] ` <1425666099-8365-1-git-send-email-sebastien.szymanski-d2DlULPkwbNWk0Htik3J/w@public.gmane.org>
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 [this message]
2015-03-07 22:02 ` Dmitry Torokhov
2015-03-07 22:12 ` Paul Bolle
2015-03-07 22:26 ` Dmitry Torokhov
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=1425765281.2300.17.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--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=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;
as well as URLs for NNTP newsgroup(s).