devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Oleksij Rempel <linux@rempel-privat.de>
Cc: linus.walleij@linaro.org, linux-gpio@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] pinctrl: Add driver for Alphascale asm9260 pinctrl
Date: Mon, 06 Apr 2015 11:41:05 +0200	[thread overview]
Message-ID: <1428313265.634.112.camel@x220> (raw)
In-Reply-To: <55224604.8070009@rempel-privat.de>

On Mon, 2015-04-06 at 10:38 +0200, Oleksij Rempel wrote:
> If you won't to say: "You have a mismatch between header and
> MODULE_LICENSE, please make sure it will match."
> You saying some thing like this: "I was right last time. Make module
> License like I saying."

No, that's not what I wrote.

> I'm confuse, what is your actual point? Do you trying to prove some thing?

My point is that there's a mismatch between the license described in the
comment at the top of this file and the ident used in the
MODULE_LICENSE() macro. In my comments on v2 I wrote:
    By the way, you probably want to use "GPL v2" as the license ident
    [...].

In this v3 I noticed the same mismatch (which was not surprising because
you already stated that "GPL" actually did match what's stated at the
comment in the top of this file). Therefor I wrote:
    So only "GPL v2" matches what's found in the comment at top of this
    file.

There now seem to be a few options:
- change either the comment at the top of this file or the license ident
used in MODULE_LICENSE() to make them actually match;
- show that I misread the comment at top of this file;
- or show that my reading of module.h is incorrect.

(Another option would be a patch that somehow merges the "GPL" and "GPL
v2" license idents. That patch would put an end to discussions like the
one we're having here. I'm _not_ volunteering to submit it.)

Thanks,


Paul Bolle


  reply	other threads:[~2015-04-06  9:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACRpkdbKLkMB6WP0zp2xN+gM4ytvs=3V5hh8uKt8e=YE4gAAqQ@mail.gmail.com>
2015-03-27  9:36 ` [PATCH v2 0/2] Add driver and documentation for Alphascale asm9260 pinctrl Oleksij Rempel
2015-03-27  9:36   ` [PATCH v2 1/2] pinctrl: Add driver " Oleksij Rempel
2015-03-27 17:10     ` Paul Bolle
2015-04-05  5:49       ` Oleksij Rempel
2015-04-05  6:16       ` Oleksij Rempel
2015-04-05  6:26       ` [PATCH v3 0/2] Add driver and documentation " Oleksij Rempel
2015-04-05  6:26         ` [PATCH v3 1/2] pinctrl: Add driver " Oleksij Rempel
2015-04-06  7:42           ` Paul Bolle
2015-04-06  8:38             ` Oleksij Rempel
2015-04-06  9:41               ` Paul Bolle [this message]
2015-04-06  9:45                 ` Oleksij Rempel
2015-04-06  9:04             ` [PATCH v4 0/2] Add driver and documentation " Oleksij Rempel
2015-04-06  9:04               ` [PATCH v4 1/2] pinctrl: Add driver " Oleksij Rempel
2015-05-05 15:12                 ` Linus Walleij
2015-05-12 16:25                   ` Oleksij Rempel
2015-05-13 11:00                     ` Linus Walleij
2015-05-14  7:26                       ` Oleksij Rempel
2015-09-09  5:55                       ` Oleksij Rempel
2015-09-25 17:14                         ` Linus Walleij
2015-04-06  9:04               ` [PATCH v4 2/2] pinctrl: asm9260: add pinctrl add device tree bindings documentation Oleksij Rempel
2015-05-05 14:46                 ` Linus Walleij
2015-05-12 16:02                   ` Oleksij Rempel
2015-04-22 19:49               ` [PATCH v4 0/2] Add driver and documentation for Alphascale asm9260 pinctrl Oleksij Rempel
2015-05-05 14:41                 ` Linus Walleij
     [not found]         ` <1428215185-14190-1-git-send-email-linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
2015-04-05  6:26           ` [PATCH v3 2/2] pinctrl: asm9260: add pinctrl add device tree bindings documentation Oleksij Rempel
2015-03-27  9:36   ` [PATCH v2 " Oleksij Rempel

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=1428313265.634.112.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=devicetree@vger.kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rempel-privat.de \
    /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).