public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-s390@vger.kernel.org, schwidefsky@de.ibm.com,
	linux-kernel@vger.kernel.org,
	Julian Wiedmann <jwi@linux.vnet.ibm.com>,
	Ursula Braun <ubraun@linux.vnet.ibm.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Kate Stewart <kstewart@linuxfoundation.org>,
	Philippe Ombredanne <pombredanne@nexb.com>
Subject: Re: [PATCH 5/9] s390: net: add SPDX identifiers to the remaining files
Date: Tue, 14 Nov 2017 21:22:49 +0100	[thread overview]
Message-ID: <20171114202249.GA3059@osiris> (raw)
In-Reply-To: <20171114173808.25092-6-gregkh@linuxfoundation.org>

On Tue, Nov 14, 2017 at 06:38:04PM +0100, Greg Kroah-Hartman wrote:
> It's good to have SPDX identifiers in all files to make it easier to
> audit the kernel tree for correct licenses.
> 
> Update the drivers/s390/net/ files with the correct SPDX license
> identifier based on the license text in the file itself.  The SPDX
> identifier is a legally binding shorthand, which can be used instead of
> the full boiler plate text.
> 
> This work is based on a script and data from Thomas Gleixner, Philippe
> Ombredanne, and Kate Stewart.
> 
> Cc: Julian Wiedmann <jwi@linux.vnet.ibm.com>
> Cc: Ursula Braun <ubraun@linux.vnet.ibm.com>
> Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
> Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Kate Stewart <kstewart@linuxfoundation.org>
> Cc: Philippe Ombredanne <pombredanne@nexb.com>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
> diff --git a/drivers/s390/net/fsm.c b/drivers/s390/net/fsm.c
> index 8c14c6c3ad3d..f0c7c182b077 100644
> --- a/drivers/s390/net/fsm.c
> +++ b/drivers/s390/net/fsm.c
> @@ -1,3 +1,4 @@
>
> +// SPDX-License-Identifier: GPL-2.0
>  /**
>   * A generic FSM based on fsm used in isdn4linux
>   *

What's the rationale to add GPL-2.0 to this file? This seems to be a bit
confusing since this file has no explicit license template, except this
one:

MODULE_LICENSE("GPL");

Which, according to include/linux/module.h translates to
    "GPL" [GNU Public License v2 or later]

On the other hand there are files like drivers/s390/char/zcore.c which just
contain a statement "License: GPL", which was converted to GPL-1.0+ (see
patch 4 of this series).
Right now I'm not saying that anything is wrong here, but I'd like to
understand the rationale.

  reply	other threads:[~2017-11-14 20:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14 17:37 [PATCH 0/9] drivers/s390/ license text cleanup Greg Kroah-Hartman
2017-11-14 17:38 ` [PATCH 1/9] s390: block: add SPDX identifiers to the remaining files Greg Kroah-Hartman
2017-11-14 17:38 ` [PATCH 2/9] s390: crypto: " Greg Kroah-Hartman
2017-11-14 17:38 ` [PATCH 3/9] s390: cio: " Greg Kroah-Hartman
2017-11-14 17:58   ` Cornelia Huck
2017-11-14 17:38 ` [PATCH 4/9] s390: char: " Greg Kroah-Hartman
2017-11-14 17:38 ` [PATCH 5/9] s390: net: " Greg Kroah-Hartman
2017-11-14 20:22   ` Heiko Carstens [this message]
2017-11-15  9:22     ` Greg Kroah-Hartman
2017-11-14 17:38 ` [PATCH 6/9] s390: scsi: zfcp_aux: add SPDX identifier Greg Kroah-Hartman
2017-11-14 17:38 ` [PATCH 7/9] s390: virtio: add SPDX identifiers to the remaining files Greg Kroah-Hartman
2017-11-14 18:00   ` Cornelia Huck
2017-11-14 17:38 ` [PATCH 8/9] s390: crypto: Remove redundant license text Greg Kroah-Hartman
2017-11-14 17:38 ` [PATCH 9/9] s390: drivers: " Greg Kroah-Hartman
2017-11-14 18:00   ` Cornelia Huck
2017-11-24 11:23 ` [PATCH 0/9] drivers/s390/ license text cleanup Heiko Carstens
2017-11-24 11:45   ` Greg Kroah-Hartman
2017-11-24 11:52     ` Heiko Carstens
2017-11-24 12:09       ` Greg Kroah-Hartman
2017-11-24 14:01       ` Greg Kroah-Hartman

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=20171114202249.GA3059@osiris \
    --to=heiko.carstens@de.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jwi@linux.vnet.ibm.com \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pombredanne@nexb.com \
    --cc=schwidefsky@de.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=ubraun@linux.vnet.ibm.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