Linux-SPDX Archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>, "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-block@vger.kernel.org, linux-spdx@vger.kernel.org
Subject: SPDX tag and top of file comment cleanups for the loop driver
Date: Tue, 19 Apr 2022 08:32:59 +0200	[thread overview]
Message-ID: <20220419063303.583106-1-hch@lst.de> (raw)

Hi Jens, hi Ted,

the loop driver still had no SPDX tag, so this series cleans up some
lose ends and fixes that up.

Ted, does the SPDX tag match your original licensing decision back then,
or do we need to correct it?  Does the auto-converted tag on the loop.h
SPDX header (GPL1.0 or later with syscall exception) make sense, or
should that have been GPL2 only with syscall exception?

             reply	other threads:[~2022-04-19  6:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19  6:32 Christoph Hellwig [this message]
2022-04-19  6:33 ` [PATCH 1/4] loop: remove loop.h Christoph Hellwig
2022-04-19 22:32   ` Chaitanya Kulkarni
2022-05-10 12:30   ` Jens Axboe
2022-04-19  6:33 ` [PATCH 2/4] loop: add a SPDX header Christoph Hellwig
2022-04-19  6:33 ` [PATCH 3/4] loop: remove most the top-of-file boilerplate comment Christoph Hellwig
2022-04-19 22:33   ` Chaitanya Kulkarni
2022-04-19  6:33 ` [PATCH 4/4] loop: remove most the top-of-file boilerplate comment from the UAPI header Christoph Hellwig
2022-05-03 20:06 ` SPDX tag and top of file comment cleanups for the loop driver Theodore Ts'o
2022-05-03 20:13   ` Christoph Hellwig
2022-05-03 21:35     ` tytso
2022-05-10  7:22       ` Christoph Hellwig
2022-05-10 12:29         ` Jens Axboe
2022-05-10 13:58           ` Theodore Ts'o

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=20220419063303.583106-1-hch@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-spdx@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).