devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: 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 18:53:39 +0200	[thread overview]
Message-ID: <1429894419.2927.61.camel@x220> (raw)
In-Reply-To: <6ED8E3B22081A4459DAC7699F3695FB7014B217581@SW-EX-MBX02.diasemi.com>

On Fri, 2015-04-24 at 13:45 +0000, Opensource [Steve Twiss] wrote:
> That seems to be a fairly common mistake in the kernel. 

It's an easy mistake to make. And as long as people pick an ident that
passes license_is_gpl_compatible() the module will build and load just
fine.

> When I did a
> straw-poll,  around 10% of files came up with "GPL v2" and contained
>  "any later version" text.

That seems plausible.

I'm inclined to think the difference between "GPL" and "GPL v2" is
mainly an accident of history (see https://lkml.org/lkml/2015/3/11/188
for some background). But apparently were stuck with these two idents.
Anyhow, in the last two months I've not come up with a better plan than
regularly check patches for mismatches like the one you made. If you
have a better idea, I'll be all ears.

Thanks,


Paul Bolle

  reply	other threads:[~2015-04-24 16:53 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 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]
     [not found]   ` <b9068c6e41a08b620c9e1674e17e508ab0d76d55.1429272200.git.stwiss.opensource-WBD+wuPFNBhBDgjK7y7TUQ@public.gmane.org>
2015-04-18  7:55     ` Paul Bolle
2015-04-24 13:45       ` Opensource [Steve Twiss]
2015-04-24 16:53         ` Paul Bolle [this message]
2015-04-28 11:56   ` Lee Jones
2015-04-29 16:01     ` Opensource [Steve Twiss]
2015-04-29 16:15       ` Lee Jones
2015-04-17 12:03 ` [RESEND PATCH V2 2/2] devicetree: Add bindings for DA9063 OnKey S Twiss

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=1429894419.2927.61.camel@x220 \
    --to=pebolle@tiscali.nl \
    --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=robh+dt@kernel.org \
    --cc=sameo@linux.intel.com \
    --cc=stwiss.opensource@diasemi.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).