linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Philippe Ombredanne <pombredanne@nexb.com>
Cc: Martin Kepplinger <martink@posteo.de>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] input: pegasus_notetaker: add license information
Date: Sun, 26 Nov 2017 09:59:51 +0100	[thread overview]
Message-ID: <20171126085951.GA10018@kroah.com> (raw)
In-Reply-To: <20171126004259.xjl2icw3gbyg3hck@dtor-ws>

On Sat, Nov 25, 2017 at 04:42:59PM -0800, Dmitry Torokhov wrote:
> Hi Martin,
> 
> On Sat, Nov 18, 2017 at 09:45:18AM +0100, Martin Kepplinger wrote:
> > This adds an SPDX license identifier to this driver I wrote some time back.
> > 
> > Signed-off-by: Martin Kepplinger <martink@posteo.de>
> > ---
> >  drivers/input/tablet/pegasus_notetaker.c | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/drivers/input/tablet/pegasus_notetaker.c b/drivers/input/tablet/pegasus_notetaker.c
> > index 47de5a81172f..cdf75c989469 100644
> > --- a/drivers/input/tablet/pegasus_notetaker.c
> > +++ b/drivers/input/tablet/pegasus_notetaker.c
> > @@ -1,3 +1,4 @@
> > +// SPDX-License-Identifier: GPL-2.0
> 
> Should this be GPL-2.0+? The MODULE_LICENSE specifies that the module is
> "GPL" which in kernel land means GPLv2+. Or we should change the module
> license to strict "GPLv2"?

That is up to Martin, given that he is the author, as to what he wants
to mark this as.  Odd that it missed the big "fix up all files with no
license information" sweep.

Philippe, how did we miss this one?

> Also, why do we use C++ -style comments for this?

That is what Linus wants, see the thread on lkml in the past few hours
for his reasoning here.

> Greg, do you have any plans on dropping MODULE_LICENSE() altogether and
> generating the appropriate string from SPDX markings in the source?

At this time, no, it's not a simple solution as it gets messy quickly
(multiple c files make up modulues, what about .h files, etc...)

> Doing this would prevent mismatches between license notices, SPDX tags
> and MODULE_LCENSE() strings, which happen very often.

I agree, but now that we are getting SPDX tags, we can fix up all of the
mismatches in MODULE_LICENSE() strings, of which there are a lot.

thanks,

greg k-h

  reply	other threads:[~2017-11-26  8:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-18  8:45 [PATCH] input: pegasus_notetaker: add license information Martin Kepplinger
2017-11-26  0:42 ` Dmitry Torokhov
2017-11-26  8:59   ` Greg Kroah-Hartman [this message]
2017-11-26 11:28     ` Philippe Ombredanne
2017-11-27  7:55       ` Greg Kroah-Hartman
2017-11-27  7:44   ` [PATCH v2] " Martin Kepplinger
2017-11-27  7:52     ` Greg KH
2017-11-27  8:02       ` [PATCH v3] " Martin Kepplinger
2017-11-27  8:07         ` Greg KH
2017-11-27 10:19         ` Philippe Ombredanne

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=20171126085951.GA10018@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martink@posteo.de \
    --cc=pombredanne@nexb.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).