From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 11/13] nvme-loop: convert to SPDX identifiers
Date: Tue, 19 Feb 2019 08:22:42 -0700 [thread overview]
Message-ID: <20190219152244.17441-12-hch@lst.de> (raw)
In-Reply-To: <20190219152244.17441-1-hch@lst.de>
Update license to use SPDX-License-Identifier instead of verbose license
text.
Signed-off-by: Christoph Hellwig <hch at lst.de>
---
drivers/nvme/target/loop.c | 10 +---------
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/drivers/nvme/target/loop.c b/drivers/nvme/target/loop.c
index 4aac1b4a8112..b9f623ab01f3 100644
--- a/drivers/nvme/target/loop.c
+++ b/drivers/nvme/target/loop.c
@@ -1,15 +1,7 @@
+// SPDX-License-Identifier: GPL-2.0
/*
* NVMe over Fabrics loopback device.
* Copyright (c) 2015-2016 HGST, a Western Digital Company.
- *
- * 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.
*/
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
#include <linux/scatterlist.h>
--
2.20.1
next prev parent reply other threads:[~2019-02-19 15:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 15:22 conver the nvme code to SPDX identifiers Christoph Hellwig
2019-02-19 15:22 ` [PATCH 01/13] nvme_ioctl.h: remove duplicate GPL boilerplate Christoph Hellwig
2019-02-19 15:22 ` [PATCH 02/13] nvme-tcp.h: fix SPDX header Christoph Hellwig
2019-02-19 15:22 ` [PATCH 03/13] nvme-fabrics: convert to SPDX identifiers Christoph Hellwig
2019-02-19 15:22 ` [PATCH 04/13] nvme-fc: " Christoph Hellwig
2019-02-19 15:22 ` [PATCH 05/13] nvme-rdma: " Christoph Hellwig
2019-02-19 15:22 ` [PATCH 06/13] nvme-lightnvm: " Christoph Hellwig
2019-02-19 15:22 ` [PATCH 07/13] nvme-pci: " Christoph Hellwig
2019-02-19 15:22 ` [PATCH 08/13] nvme: " Christoph Hellwig
2019-02-19 15:22 ` [PATCH 09/13] nvmet-fc: " Christoph Hellwig
2019-02-19 15:22 ` [PATCH 10/13] nvmet-fcloop: " Christoph Hellwig
2019-02-19 15:22 ` Christoph Hellwig [this message]
2019-02-19 15:22 ` [PATCH 12/13] nvmet-rdma: " Christoph Hellwig
2019-02-19 15:22 ` [PATCH 13/13] nvmet: " Christoph Hellwig
2019-02-19 15:33 ` conver the nvme code " Christoph Hellwig
2019-02-19 19:40 ` Sagi Grimberg
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=20190219152244.17441-12-hch@lst.de \
--to=hch@lst.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