All of lore.kernel.org
 help / color / mirror / Atom feed
From: tytso <tytso@mit.edu>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, linux-spdx@vger.kernel.org
Subject: Re: SPDX tag and top of file comment cleanups for the loop driver
Date: Tue, 3 May 2022 14:35:59 -0700	[thread overview]
Message-ID: <YnGgP7ubsXxFTaZE@mit.edu> (raw)
In-Reply-To: <20220503201334.GA7325@lst.de>

On Tue, May 03, 2022 at 10:13:34PM +0200, Christoph Hellwig wrote:
> On Tue, May 03, 2022 at 04:06:28PM -0400, Theodore Ts'o wrote:
> > > 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?
> > 
> > I think you've removed the loop.h in the patch series, so it shouldn't
> > matter what the tag would be for loop.h, right?  In any case, GPLv2
> > only was certainly the intent at the time.
> 
> Well, there were two loop.h files - drivers/block/loop.h gets removed
> in this series, but include/uapi/linux/loop.h stays.

Ah, thanks for the clarification.  Yes, GPLv2 with the syscall
extension is what would be appropriate for include/uapi/linux/loop.h.

	     	  	   	       - Ted


  reply	other threads:[~2022-05-03 21:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19  6:32 SPDX tag and top of file comment cleanups for the loop driver Christoph Hellwig
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 [this message]
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=YnGgP7ubsXxFTaZE@mit.edu \
    --to=tytso@mit.edu \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-spdx@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.