public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Josef Bacik <jbacik@fb.com>,
	Paolo Valente <paolo.valente@linaro.org>,
	Damien Le Moal <Damien.LeMoal@wdc.com>,
	Andrea Arcangeli <aarcange@redhat.com>,
	Vivek Goyal <vgoyal@redhat.com>,
	Fabio Checconi <fabio@gandalf.sssup.it>,
	Nauman Rafique <nauman@google.com>,
	Arianna Avanzini <avanzini.arianna@gmail.com>,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: add SPDX tags to all block layer files
Date: Tue, 30 Apr 2019 14:42:38 -0400	[thread overview]
Message-ID: <20190430184243.23436-1-hch@lst.de> (raw)

Hi Jens,

this series adds SPDX tags to all block layer files that are still
missing them.  The last patch adds them to files that didn't have
any licensing, and I've cced everyone who is mentioned in the
Copyright notices for these files to make sure no one has any
disagreement with the fact that that they are per default under
the kernels GPLv2 license.

             reply	other threads:[~2019-04-30 18:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-30 18:42 Christoph Hellwig [this message]
2019-04-30 18:42 ` [PATCH 1/5] block: switch all files cleared marked as GPLv2 to SPDX tags Christoph Hellwig
2019-04-30 21:38   ` Chaitanya Kulkarni
2019-04-30 18:42 ` [PATCH 2/5] block: switch all files cleared marked as GPLv2 or later " Christoph Hellwig
2019-04-30 21:38   ` Chaitanya Kulkarni
2019-04-30 18:42 ` [PATCH 3/5] sed-opal.h: remove redundant licence boilerplate Christoph Hellwig
2019-04-30 21:38   ` Chaitanya Kulkarni
2019-04-30 18:42 ` [PATCH 4/5] block: add a SPDX tag to blk-mq-rdma.h Christoph Hellwig
2019-04-30 21:39   ` Chaitanya Kulkarni
2019-04-30 18:42 ` [PATCH 5/5] block: add SPDX tags to block layer files missing licensing information Christoph Hellwig
2019-04-30 21:39   ` Chaitanya Kulkarni
2019-04-30 22:12 ` add SPDX tags to all block layer files Jens Axboe

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=20190430184243.23436-1-hch@lst.de \
    --to=hch@lst.de \
    --cc=Damien.LeMoal@wdc.com \
    --cc=aarcange@redhat.com \
    --cc=avanzini.arianna@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=fabio@gandalf.sssup.it \
    --cc=jbacik@fb.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nauman@google.com \
    --cc=paolo.valente@linaro.org \
    --cc=vgoyal@redhat.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