From: James Bottomley <jejb@linux.vnet.ibm.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>,
Avri Altman <avri.altman@wdc.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
Pedro Sousa <pedrom.sousa@synopsys.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avi Shchislowski <avi.shchislowski@wdc.com>,
Alex Lemberg <alex.lemberg@wdc.com>
Subject: Re: [PATCH] scsi: uapi: ufs: Fix SPDX license identifier
Date: Thu, 11 Jul 2019 17:20:15 -0700 [thread overview]
Message-ID: <1562890815.2915.13.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <yq1ef2w9kig.fsf@oracle.com>
On Thu, 2019-07-11 at 20:14 -0400, Martin K. Petersen wrote:
> Avri,
>
> > added 'WITH Linux-syscall-note' exception, which is the officially
> > assigned exception identifier for the kernel syscall exception.
> > This exception makes it possible to include GPL headers into non
> > GPL code, without confusing license compliance tools.
>
> I'd like Arnd to ack the license change since he has made changes
> (however mechanical) to the file.
Just to note: this isn't technically a licence change at all. The
entire kernel is covered by the system call exception and this file is
thus also covered. It's really a simple tag change to allow tools
which parse uapi header files to recognise from the SPDX tags that this
is a kernel header to which the Linux-syscall-note applies.
James
next prev parent reply other threads:[~2019-07-12 0:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 13:34 [PATCH] scsi: uapi: ufs: Fix SPDX license identifier Avri Altman
2019-06-27 5:38 ` Avri Altman
2019-06-28 11:25 ` Pedro Sousa
2019-07-04 7:47 ` Avri Altman
2019-07-12 0:14 ` Martin K. Petersen
2019-07-12 0:20 ` James Bottomley [this message]
2019-07-12 1:22 ` Martin K. Petersen
2019-07-18 6:46 ` Avri Altman
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=1562890815.2915.13.camel@linux.vnet.ibm.com \
--to=jejb@linux.vnet.ibm.com \
--cc=alex.lemberg@wdc.com \
--cc=alim.akhtar@samsung.com \
--cc=arnd@arndb.de \
--cc=avi.shchislowski@wdc.com \
--cc=avri.altman@wdc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=pedrom.sousa@synopsys.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;
as well as URLs for NNTP newsgroup(s).