From: Joe Perches <joe@perches.com>
To: Rob Herring <robh@kernel.org>
Cc: Igor Stoppa <igor.stoppa@huawei.com>,
Kate Stewart <kstewart@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andy Whitcroft <apw@canonical.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Philippe Ombredanne <pombredanne@nexb.com>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v6] checkpatch.pl: Add SPDX license tag check
Date: Fri, 02 Feb 2018 13:10:02 -0800 [thread overview]
Message-ID: <1517605802.7489.164.camel@perches.com> (raw)
In-Reply-To: <CAL_JsqJDgNrpfhg_5bL0VywJ9zFLbO+aCJsCKow9YPSJnB8huw@mail.gmail.com>
On Fri, 2018-02-02 at 14:57 -0600, Rob Herring wrote:
> On Fri, Feb 2, 2018 at 1:06 PM, Joe Perches <joe@perches.com> wrote:
[]
> > Right now, there are many missing licenses
> > that are already used by various existing
> > SPDX-License-Identifier: entries.
> >
> > APACHE-2.0
>
> Given that Apache 2.0 is not compatible with GPL 2, that would pretty
> much mean anything with Apache license is dual licensed and it would
> be the other license that applies. Do we really want/need license
> texts for all the other possible licenses that don't apply to kernel
> files?
There are 2 uses of SPDX.*Apache in staging.
drivers/staging/android/ashmem.h:// SPDX-License-Identifier: (GPL-2.0 OR Apache-2.0)
drivers/staging/android/uapi/ashmem.h:// SPDX-License-Identifier: (GPL-2.0 OR Apache-2.0)
I believe each specific license text should be
available in either the actual source file with
the Apache license or in a specific LICENSES/
file in the kernel tree.
> If so,
> this should all just be scripted to sync LICENSES/ with
> found SPDX tags in the kernel.
Right. That's probably best.
> ISC and OpenSSL are only in license-rules.rst as examples. We should
> just fix those examples to something else.
Sounds good to me.
I should have excluded Documentation/process/license-rules.rst
from the SPDX matches.
Are significant portions of that document generic across
multiple projects or is it entirely specific to linux?
cheers, Joe
next prev parent reply other threads:[~2018-02-02 21:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 15:40 Rob Herring
2018-02-02 15:49 ` Igor Stoppa
2018-02-02 16:12 ` Greg Kroah-Hartman
2018-02-02 16:17 ` Jonathan Corbet
2018-02-02 18:27 ` Rob Herring
2018-02-02 19:06 ` Joe Perches
2018-02-02 20:18 ` Kate Stewart
2018-02-02 20:26 ` Kate Stewart
2018-02-02 20:55 ` Joe Perches
2018-02-08 14:41 ` Philippe Ombredanne
2018-02-02 20:57 ` Rob Herring
2018-02-02 21:10 ` Joe Perches [this message]
2018-02-03 13:41 ` Igor Stoppa
2018-02-08 14:44 ` Philippe Ombredanne
2018-02-08 14:35 ` Philippe Ombredanne
2018-02-08 17:24 ` Joe Perches
2018-02-08 18:09 ` Philippe Ombredanne
2018-02-02 21:18 ` Joe Perches
2018-02-09 0:35 ` Joe Perches
2018-02-09 5:58 ` Philippe Ombredanne
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=1517605802.7489.164.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=igor.stoppa@huawei.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pombredanne@nexb.com \
--cc=robh@kernel.org \
--cc=tglx@linutronix.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
Powered by JetHome