devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 23:38:55 +0100	[thread overview]
Message-ID: <1425767935.2300.48.camel@x220> (raw)
In-Reply-To: <FACD03DB-5CFC-4C18-A185-1031903E3AAE@gmail.com>

On Sat, 2015-03-07 at 14:26 -0800, Dmitry Torokhov wrote:
> On March 7, 2015 2:12:20 PM PST, Paul Bolle <pebolle@tiscali.nl> wrote:
> I was talking about them being treated differently from technological
> standpoint (i.e. the code), not from legal one.

>From a technological standpoint it would be easy to declare "GPL" (or
any other string) to mean "GPL v2 compatible", which is, I think, all
that matters. But license_is_gpl_compatible() doesn't do that. And I
fear that's for a reason. Is my fear unfounded?

> 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.

checkpatch.pl crossed my mind too. But in just over a week of checking
the license comments of (a subset of) the submitted patches I've come to
think that just won't work.


Paul Bolle


  reply	other threads:[~2015-03-07 22:38 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
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 [this message]
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=1425767935.2300.48.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).