public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Ong Boon Leong <boon.leong.ong@intel.com>
Cc: rui.zhang@intel.com, edubezval@gmail.com,
	pure.logic@nexus-software.ie, hock.leong.kweh@intel.com,
	andy.shevchenko@gmail.com, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCHv4 1/1] thermal: intel Quark SoC X1000 DTS thermal driver
Date: Sat, 11 Apr 2015 12:04:11 +0200	[thread overview]
Message-ID: <1428746651.17822.83.camel@x220> (raw)
In-Reply-To: <1428638821-9737-2-git-send-email-boon.leong.ong@intel.com>

There might be a mismatch between the license stated in the comment at
the top of the (only) source file of this driver and the license ident
used in the MODULE_LICENSE() macro.

On Fri, 2015-04-10 at 12:07 +0800, Ong Boon Leong wrote:
> --- /dev/null
> +++ b/drivers/thermal/intel_quark_dts_thermal.c

> + * This program is free software; you can redistribute it and/or modify it
> + * under the terms and conditions of the GNU General Public License,
> + * version 2, as published by the Free Software Foundation.
> + *
> + * This program is distributed in the hope it will be useful, but WITHOUT
> + * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
> + * FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for
> + * more details.

This only states the license is GPL v2.

> +MODULE_LICENSE("Dual BSD/GPL");

And this states that there's a "GNU Public License v2 or BSD license
choice". But if that's what you want, shouldn't the BSD license be
copied in that comment too? (Please note that this is not a rhetorical
question.)

Thanks,


Paul Bolle


      reply	other threads:[~2015-04-11 10:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10  4:07 [PATCHv4 0/1] Intel Quark X1000 DTS thermal driver Ong Boon Leong
2015-04-10  4:07 ` [PATCHv4 1/1] thermal: intel Quark SoC " Ong Boon Leong
2015-04-11 10:04   ` Paul Bolle [this message]

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=1428746651.17822.83.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=andy.shevchenko@gmail.com \
    --cc=boon.leong.ong@intel.com \
    --cc=edubezval@gmail.com \
    --cc=hock.leong.kweh@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pure.logic@nexus-software.ie \
    --cc=rui.zhang@intel.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