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>
Subject: Re: [PATCH V1 1/2] input: misc: da9063: OnKey driver
Date: Thu, 09 Apr 2015 10:47:53 +0200 [thread overview]
Message-ID: <1428569273.14000.17.camel@x220> (raw)
In-Reply-To: <0219212ab4e2b01256f2dac92d9a0d848c44197a.1428504804.git.stwiss.opensource@diasemi.com>
A license mismatch was all I spotted.
On Wed, 2015-04-08 at 15:53 +0100, Steve Twiss wrote:
> From: Steve Twiss <stwiss.opensource@diasemi.com>
>
> Add OnKey driver support for DA9063
>
> This patch is dependent on PATCH V1 2/2
(But I also spotted this line. And then I checked 2/2, which has:
This patch is dependent on PATCH V1 1/2
Which makes it all rather confusing.
Anyhow, neither patch should need to carry such a line. The 1/2 and 2/2
in the Subject: line should suffice.)
> Signed-off-by: Steve Twiss <stwiss.opensource@diasemi.com>
>
> ---
> This patch applies against linux-next and v4.0-rc6
> --- /dev/null
> +++ b/drivers/input/misc/da9063-onkey.c
> @@ -0,0 +1,227 @@
> +/* da9063-onkey.c - Onkey device driver for DA9063
> + * Copyright (C) 2013 Dialog Semiconductor Ltd.
> + *
> + * This library is free software; you can redistribute it and/or
> + * modify it under the terms of the GNU Library General Public
> + * License as published by the Free Software Foundation; either
> + * version 2 of the License, or (at your option) any later version.
> + *
> + * This library is distributed in the hope that it will be useful,
> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
> + * Library General Public License for more details.
> + */
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.
Paul Bolle
next prev parent reply other threads:[~2015-04-09 8:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 14:53 [PATCH V1 0/2] Add OnKey support for DA9063 Steve Twiss
2015-04-08 14:53 ` [PATCH V1 1/2] input: misc: da9063: OnKey driver Steve Twiss
2015-04-09 8:47 ` Paul Bolle [this message]
2015-04-09 10:12 ` Opensource [Steve Twiss]
2015-04-09 12:01 ` Paul Bolle
2015-04-08 14:53 ` [PATCH V1 2/2] devicetree: Add bindings for DA9063 OnKey Steve Twiss
2015-04-09 9:21 ` Lee Jones
2015-04-09 10:31 ` Opensource [Steve 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=1428569273.14000.17.camel@x220 \
--to=pebolle@tiscali.nl \
--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