From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-s390@vger.kernel.org, schwidefsky@de.ibm.com,
heiko.carstens@de.ibm.com
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Steffen Maier <maier@linux.vnet.ibm.com>,
Benjamin Block <bblock@linux.vnet.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <kstewart@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>
Subject: [PATCH 6/9] s390: scsi: zfcp_aux: add SPDX identifier
Date: Tue, 14 Nov 2017 18:38:05 +0100 [thread overview]
Message-ID: <20171114173808.25092-7-gregkh@linuxfoundation.org> (raw)
In-Reply-To: <20171114173808.25092-1-gregkh@linuxfoundation.org>
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/scsi/zfcp_aux.c file 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: Steffen Maier <maier@linux.vnet.ibm.com>
Cc: Benjamin Block <bblock@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>
---
drivers/s390/scsi/zfcp_aux.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/s390/scsi/zfcp_aux.c b/drivers/s390/scsi/zfcp_aux.c
index 84752152d41f..a3a8c8d9d717 100644
--- a/drivers/s390/scsi/zfcp_aux.c
+++ b/drivers/s390/scsi/zfcp_aux.c
@@ -1,3 +1,4 @@
+// SPDX-License-Identifier: GPL-2.0
/*
* zfcp device driver
*
--
2.15.0
next prev parent reply other threads:[~2017-11-14 17:39 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
2017-11-15 9:22 ` Greg Kroah-Hartman
2017-11-14 17:38 ` Greg Kroah-Hartman [this message]
2017-11-14 17:38 ` [PATCH 7/9] s390: virtio: " 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=20171114173808.25092-7-gregkh@linuxfoundation.org \
--to=gregkh@linuxfoundation.org \
--cc=bblock@linux.vnet.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=maier@linux.vnet.ibm.com \
--cc=pombredanne@nexb.com \
--cc=schwidefsky@de.ibm.com \
--cc=tglx@linutronix.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