From: hch@lst.de (Christoph Hellwig)
Subject: conver the nvme code to SPDX identifiers
Date: Tue, 19 Feb 2019 16:33:53 +0100 [thread overview]
Message-ID: <20190219153353.GA4570@lst.de> (raw)
In-Reply-To: <20190219152244.17441-1-hch@lst.de>
Adding James for nvme-fc.
On Tue, Feb 19, 2019@08:22:31AM -0700, Christoph Hellwig wrote:
> Hi all,
>
> this series converts all NVMe driver source files to SPDX identifiers,
> and also fixes up a few existing ones.
>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
---end quoted text---
next prev parent reply other threads:[~2019-02-19 15:33 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 ` [PATCH 11/13] nvme-loop: " Christoph Hellwig
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 ` Christoph Hellwig [this message]
2019-02-19 19:40 ` conver the nvme code " 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=20190219153353.GA4570@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