[patch 0/9] LICENSES: Add missing License Text and fixup bogus identifiers

[patch 0/9] LICENSES: Add missing License Text and fixup bogus identifiers

[Thomas Gleixner]

There are a few bogus SPDX identifiers in various files and SPDX
Identifiers used in tree or about to be used which have no corresponding
License Text file in the LICENSES directory or use the new variant of the
GPL-2.0[+] license identifiers which are not mentioned in the GPL-2.0
Valid-License-Identifiers: tags.

The following series cleans that up:

 - Use the proper identifiers

 - Add GPL-2.0-only and GPL-2.0-or-later identifiers to the GPL2.0 license

 - Add X11, Apache-2.0, CC-BY-SA-4.0, CCDL-1.0, Linux-OpenIB license texts
   to the LICENSES directory along with the required documentation texts

8<-------------
 LICENSES/preferred/GPL-2.0              |    6 
 arch/arm/mach-s3c24xx/h1940-bluetooth.c |    2 
 arch/x86/include/asm/jailhouse_para.h   |    2 
 arch/x86/kernel/jailhouse.c             |    2 
 b/LICENSES/other/Apache-2.0             |  183 ++++++++++++++
 b/LICENSES/other/CC-BY-SA-4.0           |  397 ++++++++++++++++++++++++++++++++
 b/LICENSES/other/CDDL-1.0               |  363 +++++++++++++++++++++++++++++
 b/LICENSES/other/Linux-OpenIB           |   26 ++
 b/LICENSES/other/X11                    |   37 ++
 drivers/pinctrl/sh-pfc/pfc-r8a77965.c   |    2 
 10 files changed, 1016 insertions(+), 4 deletions(-)

[patch 1/9] x86/jailhouse: Fix incorrect SPDX identifier

[Thomas Gleixner]

[-- Attachment #1: x86-jailhouse--Fix-incorrect-SPDX-identifier.patch --]
[-- Type: text/plain, Size: 825 bytes --]

GPL2.0 is not a valid SPDX identiier. Replace it with GPL-2.0.

Fixes: 4a362601baa6 ("x86/jailhouse: Add infrastructure for running in non-root cell")
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Jan Kiszka <jan.kiszka@siemens.com>
---
 arch/x86/include/asm/jailhouse_para.h |    2 +-
 arch/x86/kernel/jailhouse.c           |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

--- a/arch/x86/include/asm/jailhouse_para.h
+++ b/arch/x86/include/asm/jailhouse_para.h
@@ -1,4 +1,4 @@
-/* SPDX-License-Identifier: GPL2.0 */
+/* SPDX-License-Identifier: GPL-2.0 */
 
 /*
  * Jailhouse paravirt detection
--- a/arch/x86/kernel/jailhouse.c
+++ b/arch/x86/kernel/jailhouse.c
@@ -1,4 +1,4 @@
-// SPDX-License-Identifier: GPL2.0
+// SPDX-License-Identifier: GPL-2.0
 /*
  * Jailhouse paravirt_ops implementation
  *

Re: [patch 1/9] x86/jailhouse: Fix incorrect SPDX identifier

[Jan Kiszka]

On 2018-04-23 00:02, Thomas Gleixner wrote:
> GPL2.0 is not a valid SPDX identiier. Replace it with GPL-2.0.
> 
> Fixes: 4a362601baa6 ("x86/jailhouse: Add infrastructure for running in non-root cell")
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Cc: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>  arch/x86/include/asm/jailhouse_para.h |    2 +-
>  arch/x86/kernel/jailhouse.c           |    2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> --- a/arch/x86/include/asm/jailhouse_para.h
> +++ b/arch/x86/include/asm/jailhouse_para.h
> @@ -1,4 +1,4 @@
> -/* SPDX-License-Identifier: GPL2.0 */
> +/* SPDX-License-Identifier: GPL-2.0 */
>  
>  /*
>   * Jailhouse paravirt detection
> --- a/arch/x86/kernel/jailhouse.c
> +++ b/arch/x86/kernel/jailhouse.c
> @@ -1,4 +1,4 @@
> -// SPDX-License-Identifier: GPL2.0
> +// SPDX-License-Identifier: GPL-2.0
>  /*
>   * Jailhouse paravirt_ops implementation
>   *
> 
> 

Acked-by: Jan Kiszka <jan.kiszka@siemens.com>

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

[tip:x86/urgent] x86/jailhouse: Fix incorrect SPDX identifier

[tip-bot for Thomas Gleixner]

Commit-ID:  7010adcdd23527f7efef1e7bc0d8c458f6ec0dd2
Gitweb:     https://git.kernel.org/tip/7010adcdd23527f7efef1e7bc0d8c458f6ec0dd2
Author:     Thomas Gleixner <tglx@linutronix.de>
AuthorDate: Mon, 23 Apr 2018 00:02:09 +0200
Committer:  Thomas Gleixner <tglx@linutronix.de>
CommitDate: Mon, 23 Apr 2018 10:17:28 +0200

x86/jailhouse: Fix incorrect SPDX identifier

GPL2.0 is not a valid SPDX identiier. Replace it with GPL-2.0.

Fixes: 4a362601baa6 ("x86/jailhouse: Add infrastructure for running in non-root cell")
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Kate Stewart <kstewart@linuxfoundation.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Philippe Ombredanne <pombredanne@nexb.com>
Link: https://lkml.kernel.org/r/20180422220832.815346488@linutronix.de

---
 arch/x86/include/asm/jailhouse_para.h | 2 +-
 arch/x86/kernel/jailhouse.c           | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/x86/include/asm/jailhouse_para.h b/arch/x86/include/asm/jailhouse_para.h
index b885a961a150..a34897aef2c2 100644
--- a/arch/x86/include/asm/jailhouse_para.h
+++ b/arch/x86/include/asm/jailhouse_para.h
@@ -1,4 +1,4 @@
-/* SPDX-License-Identifier: GPL2.0 */
+/* SPDX-License-Identifier: GPL-2.0 */
 
 /*
  * Jailhouse paravirt detection
diff --git a/arch/x86/kernel/jailhouse.c b/arch/x86/kernel/jailhouse.c
index fa183a131edc..a15fe0e92cf9 100644
--- a/arch/x86/kernel/jailhouse.c
+++ b/arch/x86/kernel/jailhouse.c
@@ -1,4 +1,4 @@
-// SPDX-License-Identifier: GPL2.0
+// SPDX-License-Identifier: GPL-2.0
 /*
  * Jailhouse paravirt_ops implementation
  *

[patch 2/9] pinctrl: sh-pfc: r8a77965: Fixup incorrect SPDX identifier

[Thomas Gleixner]

[-- Attachment #1: pinctrl--sh-pfc--r8a77965--Fixup-incorrect-SPDX-identifier.patch --]
[-- Type: text/plain, Size: 643 bytes --]

GPL-2. is not a valid SPDX identifier. Make it GPL-2.0

Fixes: 490e687eb8b2 ("pinctrl: sh-pfc: Initial R-Car M3-N support")
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Jacopo Mondi <jacopo+renesas@jmondi.org>
Cc: Rob Herring <robh@kernel.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>
---
 drivers/pinctrl/sh-pfc/pfc-r8a77965.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/drivers/pinctrl/sh-pfc/pfc-r8a77965.c
+++ b/drivers/pinctrl/sh-pfc/pfc-r8a77965.c
@@ -1,4 +1,4 @@
-// SPDX-License-Identifier: GPL-2.
+// SPDX-License-Identifier: GPL-2.0
 /*
  * R8A77965 processor support - PFC hardware block.
  *

Re: [patch 2/9] pinctrl: sh-pfc: r8a77965: Fixup incorrect SPDX identifier

[Geert Uytterhoeven]

On Mon, Apr 23, 2018 at 12:02 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> GPL-2. is not a valid SPDX identifier. Make it GPL-2.0
>
> Fixes: 490e687eb8b2 ("pinctrl: sh-pfc: Initial R-Car M3-N support")
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Cc: Jacopo Mondi <jacopo+renesas@jmondi.org>
> Cc: Rob Herring <robh@kernel.org>
> Cc: Geert Uytterhoeven <geert+renesas@glider.be>

Thanks, will queue in sh-pfc-for-v4.18.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

[patch 3/9] ARM: S3C24XX: Fix invalid SPDX identifier

[Thomas Gleixner]

[-- Attachment #1: ARM--S3C24XX--Fix-invalid-SPDX-identifier.patch --]
[-- Type: text/plain, Size: 853 bytes --]

GPL-1.0 is not part of the valid identifier list and as its meaning is GPL
version 1.0 only this would be incompatible with the kernel license.

As this code was included into the kernel, assume its GPL-1.0+

Fixes: 84b2170109e4 ("ARM: S3C24XX: Add SPDX license identifiers")
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Arnaud Patard <arnaud.patard@rtp-net.org>
Cc: Ben Dooks <ben-linux@fluff.org>
Cc: Russell King <rmk+kernel@arm.linux.org.uk>
---
 arch/arm/mach-s3c24xx/h1940-bluetooth.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/arch/arm/mach-s3c24xx/h1940-bluetooth.c
+++ b/arch/arm/mach-s3c24xx/h1940-bluetooth.c
@@ -1,4 +1,4 @@
-// SPDX-License-Identifier: GPL-1.0
+// SPDX-License-Identifier: GPL-1.0+
 //
 // Copyright (c) Arnaud Patard <arnaud.patard@rtp-net.org>
 //

Re: [patch 3/9] ARM: S3C24XX: Fix invalid SPDX identifier

[Krzysztof Kozlowski]

On Mon, Apr 23, 2018 at 12:02:11AM +0200, Thomas Gleixner wrote:
> GPL-1.0 is not part of the valid identifier list and as its meaning is GPL
> version 1.0 only this would be incompatible with the kernel license.
> 
> As this code was included into the kernel, assume its GPL-1.0+
> 
> Fixes: 84b2170109e4 ("ARM: S3C24XX: Add SPDX license identifiers")
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Cc: Krzysztof Kozlowski <krzk@kernel.org>
> Cc: Arnaud Patard <arnaud.patard@rtp-net.org>
> Cc: Ben Dooks <ben-linux@fluff.org>
> Cc: Russell King <rmk+kernel@arm.linux.org.uk>
> ---
>  arch/arm/mach-s3c24xx/h1940-bluetooth.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

+Cc samsung-soc

Thanks, applied.

Best regards,
Krzysztof

Re: [patch 3/9] ARM: S3C24XX: Fix invalid SPDX identifier

[Christoph Hellwig]

On Mon, Apr 23, 2018 at 12:02:11AM +0200, Thomas Gleixner wrote:
> GPL-1.0 is not part of the valid identifier list and as its meaning is GPL
> version 1.0 only this would be incompatible with the kernel license.
> 
> As this code was included into the kernel, assume its GPL-1.0+
> 
> Fixes: 84b2170109e4 ("ARM: S3C24XX: Add SPDX license identifiers")

Before that commit the file just said GNU General Public License and
referred to the COPYING file.  Which to me suggests it is at best
GPL-2.0+ if not GPL-2.0.

Hopefully the original author can still be reached to clear this up.

[patch 4/9] LICENSES/GPL2.0: Add GPL-2.0-only/or-later as valid identifiers

[Thomas Gleixner]

[-- Attachment #1: LICENSES-GPL2.0--Add-GPL-2.0-only-as-valid-identifier.patch --]
[-- Type: text/plain, Size: 1401 bytes --]

Quite some files have been flagged with the new GPL-2.0-only and
GPL-2.0-or-later identifiers which replace the original GPL-2.0 and
GPL-2.0+ identifiers in the SPDX license identifier specification, but the
identifiers are not mentioned as valid in the GPL-2.0 license file.

Add them to make everything consistent again.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Hans Verkuil <hans.verkuil@cisco.com>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>
---
 LICENSES/preferred/GPL-2.0 |    6 ++++++
 1 file changed, 6 insertions(+)

--- a/LICENSES/preferred/GPL-2.0
+++ b/LICENSES/preferred/GPL-2.0
@@ -1,5 +1,7 @@
 Valid-License-Identifier: GPL-2.0
+Valid-License-Identifier: GPL-2.0-only
 Valid-License-Identifier: GPL-2.0+
+Valid-License-Identifier: GPL-2.0-or-later
 SPDX-URL: https://spdx.org/licenses/GPL-2.0.html
 Usage-Guide:
   To use this license in source code, put one of the following SPDX
@@ -7,8 +9,12 @@ SPDX-URL: https://spdx.org/licenses/GPL-
   guidelines in the licensing rules documentation.
   For 'GNU General Public License (GPL) version 2 only' use:
     SPDX-License-Identifier: GPL-2.0
+  or
+    SPDX-License-Identifier: GPL-2.0-only
   For 'GNU General Public License (GPL) version 2 or any later version' use:
     SPDX-License-Identifier: GPL-2.0+
+  or
+    SPDX-License-Identifier: GPL-2.0-or-later
 License-Text:
 
 		    GNU GENERAL PUBLIC LICENSE

Re: [patch 4/9] LICENSES/GPL2.0: Add GPL-2.0-only/or-later as valid identifiers

[Greg Kroah-Hartman]

On Mon, Apr 23, 2018 at 12:02:12AM +0200, Thomas Gleixner wrote:
> Quite some files have been flagged with the new GPL-2.0-only and
> GPL-2.0-or-later identifiers which replace the original GPL-2.0 and
> GPL-2.0+ identifiers in the SPDX license identifier specification, but the
> identifiers are not mentioned as valid in the GPL-2.0 license file.
> 
> Add them to make everything consistent again.
> 
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Cc: Hans Verkuil <hans.verkuil@cisco.com>
> Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>

As much as I dislike the "new" identifiers, I guess trying to hold them
back is a pointless exercise :(

Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Re: [patch 4/9] LICENSES/GPL2.0: Add GPL-2.0-only/or-later as valid identifiers

[Hans Verkuil]

On 23/04/18 08:52, Greg Kroah-Hartman wrote:
> On Mon, Apr 23, 2018 at 12:02:12AM +0200, Thomas Gleixner wrote:
>> Quite some files have been flagged with the new GPL-2.0-only and
>> GPL-2.0-or-later identifiers which replace the original GPL-2.0 and
>> GPL-2.0+ identifiers in the SPDX license identifier specification, but the
>> identifiers are not mentioned as valid in the GPL-2.0 license file.
>>
>> Add them to make everything consistent again.
>>
>> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
>> Cc: Hans Verkuil <hans.verkuil@cisco.com>
>> Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>
> 
> As much as I dislike the "new" identifiers, I guess trying to hold them
> back is a pointless exercise :(

I like the new identifiers :-)

Reviewed-by: Hans Verkuil <hans.verkuil@cisco.com>

Regards,

	Hans

> 
> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> 

Re: [patch 4/9] LICENSES/GPL2.0: Add GPL-2.0-only/or-later as valid identifiers

[Mauro Carvalho Chehab]

Em Mon, 23 Apr 2018 08:52:29 +0200
Greg Kroah-Hartman <gregkh@linuxfoundation.org> escreveu:

> On Mon, Apr 23, 2018 at 12:02:12AM +0200, Thomas Gleixner wrote:
> > Quite some files have been flagged with the new GPL-2.0-only and
> > GPL-2.0-or-later identifiers which replace the original GPL-2.0 and
> > GPL-2.0+ identifiers in the SPDX license identifier specification, but the
> > identifiers are not mentioned as valid in the GPL-2.0 license file.
> > 
> > Add them to make everything consistent again.
> > 
> > Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> > Cc: Hans Verkuil <hans.verkuil@cisco.com>
> > Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>  
> 
> As much as I dislike the "new" identifiers, I guess trying to hold them
> back is a pointless exercise :(

Well, it is part of the SPDX spec, so it should be valid, no matter
of personal tastes.

I'd say that we should clearly point what SPDX version is preferred at:
	Documentation/process/license-rules.rst

And, if we adopt version 3.0, change the described license tags
accordingly, as the tags showed there are for some pre-version 3.0
SPDX version (but the file doesn't mention if it follows SPDX version
1.0, 1.1, 1.2, 2.0 or 2.1).

Anyway, for this specific patch:

Reviewed-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>


Thanks,
Mauro

Re: [patch 4/9] LICENSES/GPL2.0: Add GPL-2.0-only/or-later as valid identifiers

[Thomas Gleixner]

On Mon, 23 Apr 2018, Mauro Carvalho Chehab wrote:
> Em Mon, 23 Apr 2018 08:52:29 +0200
> Greg Kroah-Hartman <gregkh@linuxfoundation.org> escreveu:
> 
> > On Mon, Apr 23, 2018 at 12:02:12AM +0200, Thomas Gleixner wrote:
> > > Quite some files have been flagged with the new GPL-2.0-only and
> > > GPL-2.0-or-later identifiers which replace the original GPL-2.0 and
> > > GPL-2.0+ identifiers in the SPDX license identifier specification, but the
> > > identifiers are not mentioned as valid in the GPL-2.0 license file.
> > > 
> > > Add them to make everything consistent again.
> > > 
> > > Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> > > Cc: Hans Verkuil <hans.verkuil@cisco.com>
> > > Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>  
> > 
> > As much as I dislike the "new" identifiers, I guess trying to hold them
> > back is a pointless exercise :(
> 
> Well, it is part of the SPDX spec, so it should be valid, no matter
> of personal tastes.
> 
> I'd say that we should clearly point what SPDX version is preferred at:
> 	Documentation/process/license-rules.rst
> 
> And, if we adopt version 3.0, change the described license tags
> accordingly, as the tags showed there are for some pre-version 3.0
> SPDX version (but the file doesn't mention if it follows SPDX version
> 1.0, 1.1, 1.2, 2.0 or 2.1).

We need to grab the new version anyway due to the new Linux-OpenIB
license ID.

And we can document that the new -only and -or-later versions are
preferred, but should we really patch thousands of files just to update the
IDs?

I don't think so, SPDX better get their act together and mark them as
equivalent.

Thanks,

	tglx

Re: [patch 4/9] LICENSES/GPL2.0: Add GPL-2.0-only/or-later as valid identifiers

[Kate Stewart]

[-- Attachment #1: Type: text/plain, Size: 663 bytes --]

On Sun, Apr 22, 2018 at 5:02 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
>
> Quite some files have been flagged with the new GPL-2.0-only and
> GPL-2.0-or-later identifiers which replace the original GPL-2.0 and
> GPL-2.0+ identifiers in the SPDX license identifier specification, but the
> identifiers are not mentioned as valid in the GPL-2.0 license file.
>
> Add them to make everything consistent again.
>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Cc: Hans Verkuil <hans.verkuil@cisco.com>
> Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>

Feel free to add my:

 Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>

Thanks, Kate

[-- Attachment #2: Type: text/html, Size: 1045 bytes --]

[patch 5/9] LICENSES: Add X11 license

[Thomas Gleixner]

[-- Attachment #1: LICENSES--Add-X11-license.patch --]
[-- Type: text/plain, Size: 2009 bytes --]

Add the full text of the X11 to the kernel tree.  It was copied directly
from:
    
   https://spdx.org/licenses/X11.html#licenseText

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
 LICENSES/other/X11 |   37 +++++++++++++++++++++++++++++++++++++
 1 file changed, 37 insertions(+)

--- /dev/null
+++ b/LICENSES/other/X11
@@ -0,0 +1,37 @@
+Valid-License-Identifier: X11
+SPDX-URL: https://spdx.org/licenses/X11.html
+Usage-Guide:
+  To use the X11 put the following SPDX tag/value pair into a comment
+  according to the placement guidelines in the licensing rules
+  documentation:
+    SPDX-License-Identifier: X11
+License-Text:
+
+
+X11 License
+
+Copyright (C) 1996 X Consortium
+
+Permission is hereby granted, free of charge, to any person obtaining a
+copy of this software and associated documentation files (the "Software"),
+to deal in the Software without restriction, including without limitation
+the rights to use, copy, modify, merge, publish, distribute, sublicense,
+and/or sell copies of the Software, and to permit persons to whom the
+Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+Except as contained in this notice, the name of the X Consortium shall not
+be used in advertising or otherwise to promote the sale, use or other
+dealings in this Software without prior written authorization from the X
+Consortium.
+
+X Window System is a trademark of X Consortium, Inc.

Re: [patch 5/9] LICENSES: Add X11 license

[Greg Kroah-Hartman]

On Mon, Apr 23, 2018 at 12:02:13AM +0200, Thomas Gleixner wrote:
> Add the full text of the X11 to the kernel tree.  It was copied directly
> from:
>     
>    https://spdx.org/licenses/X11.html#licenseText
> 
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>

Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

[patch 6/9] LICENSES: Add CDDL-1.0 license text

[Thomas Gleixner]

[-- Attachment #1: LICENSES--Add-CDDL-1.0-license-text.patch --]
[-- Type: text/plain, Size: 19875 bytes --]

Add the full text of the CDDL-1.0 to the kernel tree.  It was copied directly
from:
    
   https://spdx.org/licenses/CDDL-1.0.html#licenseText

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
 LICENSES/other/CDDL-1.0 |  363 ++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 363 insertions(+)

--- /dev/null
+++ b/LICENSES/other/CDDL-1.0
@@ -0,0 +1,363 @@
+Valid-License-Identifier: CDDL-1.0
+SPDX-URL: https://spdx.org/licenses/CDDL-1.0.html
+Usage-Guide:
+  To use the Common Development and Distribution License 1.0 put the
+  following SPDX tag/value pair into a comment according to the placement
+  guidelines in the licensing rules documentation:
+    SPDX-License-Identifier: CDDL-1.0
+
+License-Text:
+
+COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL)
+Version 1.0
+
+    1. Definitions.
+
+        1.1. "Contributor" means each individual or entity that creates or
+             contributes to the creation of Modifications.
+
+        1.2. "Contributor Version" means the combination of the Original
+	     Software, prior Modifications used by a Contributor (if any),
+	     and the Modifications made by that particular Contributor.
+
+        1.3. "Covered Software" means (a) the Original Software, or (b)
+             Modifications, or (c) the combination of files containing
+             Original Software with files containing Modifications, in each
+             case including portions thereof.
+
+	1.4. "Executable" means the Covered Software in any form other than
+             Source Code.
+
+        1.5. "Initial Developer" means the individual or entity that first
+             makes Original Software available under this License.
+
+        1.6. "Larger Work" means a work which combines Covered Software or
+             portions thereof with code not governed by the terms of this
+             License.
+
+        1.7. "License" means this document.
+
+        1.8. "Licensable" means having the right to grant, to the maximum
+             extent possible, whether at the time of the initial grant or
+             subsequently acquired, any and all of the rights conveyed herein.
+
+        1.9. "Modifications" means the Source Code and Executable form of
+             any of the following:
+
+            A. Any file that results from an addition to, deletion from or
+               modification of the contents of a file containing Original
+               Software or previous Modifications;
+
+            B. Any new file that contains any part of the Original Software
+               or previous Modification; or
+
+            C. Any new file that is contributed or otherwise made available
+               under the terms of this License.
+
+        1.10. "Original Software" means the Source Code and Executable form
+              of computer software code that is originally released under
+              this License.
+
+        1.11. "Patent Claims" means any patent claim(s), now owned or
+              hereafter acquired, including without limitation, method,
+              process, and apparatus claims, in any patent Licensable by
+              grantor.
+
+        1.12. "Source Code" means (a) the common form of computer software
+	      code in which modifications are made and (b) associated
+              documentation included in or with such code.
+
+        1.13. "You" (or "Your") means an individual or a legal entity
+              exercising rights under, and complying with all of the terms
+              of, this License. For legal entities, "You" includes any
+              entity which controls, is controlled by, or is under common
+              control with You. For purposes of this definition, "control"
+              means (a) the power, direct or indirect, to cause the
+              direction or management of such entity, whether by contract
+              or otherwise, or (b) ownership of more than fifty percent
+              (50%) of the outstanding shares or beneficial ownership of
+              such entity.
+
+    2. License Grants.
+        2.1. The Initial Developer Grant.
+
+        Conditioned upon Your compliance with Section 3.1 below and subject
+        to third party intellectual property claims, the Initial Developer
+        hereby grants You a world-wide, royalty-free, non-exclusive
+        license:
+
+            (a) under intellectual property rights (other than patent or
+            	trademark) Licensable by Initial Developer, to use,
+            	reproduce, modify, display, perform, sublicense and
+            	distribute the Original Software (or portions thereof),
+            	with or without Modifications, and/or as part of a Larger
+            	Work; and
+
+            (b) under Patent Claims infringed by the making, using or
+            	selling of Original Software, to make, have made, use,
+            	practice, sell, and offer for sale, and/or otherwise dispose of
+            	the Original Software (or portions thereof).
+
+            (c) The licenses granted in Sections 2.1(a) and (b) are
+            	effective on the date Initial Developer first distributes
+            	or otherwise makes the Original Software available to a
+            	third party under the terms of this License.
+
+            (d) Notwithstanding Section 2.1(b) above, no patent license is
+            	granted: (1) for code that You delete from the Original
+            	Software, or (2) for infringements caused by: (i) the
+            	modification of the Original Software, or (ii) the combination
+            	of the Original Software with other software or devices.
+
+        2.2. Contributor Grant.
+
+        Conditioned upon Your compliance with Section 3.1 below and subject
+        to third party intellectual property claims, each Contributor
+        hereby grants You a world-wide, royalty-free, non-exclusive
+        license:
+
+            (a) under intellectual property rights (other than patent or
+	        trademark) Licensable by Contributor to use, reproduce,
+	        modify, display, perform, sublicense and distribute the
+	        Modifications created by such Contributor (or portions
+	        thereof), either on an unmodified basis, with other
+	        Modifications, as Covered Software and/or as part of a
+	        Larger Work; and
+
+            (b) under Patent Claims infringed by the making, using, or
+            	selling of Modifications made by that Contributor either
+            	alone and/or in combination with its Contributor Version
+            	(or portions of such combination), to make, use, sell,
+            	offer for sale, have made, and/or otherwise dispose of: (1)
+            	Modifications made by that Contributor (or portions
+            	thereof); and (2) the combination of Modifications made by
+            	that Contributor with its Contributor Version (or portions
+            	of such combination).
+
+            (c) The licenses granted in Sections 2.2(a) and 2.2(b) are
+            	effective on the date Contributor first distributes or
+            	otherwise makes the Modifications available to a third
+            	party.
+
+            (d) Notwithstanding Section 2.2(b) above, no patent license is
+            	granted: (1) for any code that Contributor has deleted from
+            	the Contributor Version; (2) for infringements caused by:
+            	(i) third party modifications of Contributor Version, or
+            	(ii) the combination of Modifications made by that
+            	Contributor with other software (except as part of the
+            	Contributor Version) or other devices; or (3) under Patent
+            	Claims infringed by Covered Software in the absence of
+            	Modifications made by that Contributor.
+
+    3. Distribution Obligations.
+        3.1. Availability of Source Code.
+
+        Any Covered Software that You distribute or otherwise make
+        available in Executable form must also be made available in Source
+        Code form and that Source Code form must be distributed only under
+        the terms of this License. You must include a copy of this License
+        with every copy of the Source Code form of the Covered Software You
+        distribute or otherwise make available. You must inform recipients
+        of any such Covered Software in Executable form as to how they can
+        obtain such Covered Software in Source Code form in a reasonable
+        manner on or through a medium customarily used for software
+        exchange.
+
+        3.2. Modifications.
+
+        The Modifications that You create or to which You contribute are
+        governed by the terms of this License. You represent that You
+        believe Your Modifications are Your original creation(s) and/or You
+        have sufficient rights to grant the rights conveyed by this
+        License.
+
+        3.3. Required Notices.
+
+        You must include a notice in each of Your Modifications that
+        identifies You as the Contributor of the Modification. You may not
+        remove or alter any copyright, patent or trademark notices
+        contained within the Covered Software, or any notices of licensing
+        or any descriptive text giving attribution to any Contributor or
+        the Initial Developer.
+
+        3.4. Application of Additional Terms.
+
+        You may not offer or impose any terms on any Covered Software in
+        Source Code form that alters or restricts the applicable version of
+        this License or the recipients' rights hereunder. You may choose to
+        offer, and to charge a fee for, warranty, support, indemnity or
+        liability obligations to one or more recipients of Covered
+        Software. However, you may do so only on Your own behalf, and not
+        on behalf of the Initial Developer or any Contributor. You must
+        make it absolutely clear that any such warranty, support, indemnity
+        or liability obligation is offered by You alone, and You hereby
+        agree to indemnify the Initial Developer and every Contributor for
+        any liability incurred by the Initial Developer or such Contributor
+        as a result of warranty, support, indemnity or liability terms You
+        offer.
+
+        3.5. Distribution of Executable Versions.
+
+        You may distribute the Executable form of the Covered Software
+        under the terms of this License or under the terms of a license of
+        Your choice, which may contain terms different from this License,
+        provided that You are in compliance with the terms of this License
+        and that the license for the Executable form does not attempt to
+        limit or alter the recipient's rights in the Source Code form from
+        the rights set forth in this License. If You distribute the Covered
+        Software in Executable form under a different license, You must
+        make it absolutely clear that any terms which differ from this
+        License are offered by You alone, not by the Initial Developer or
+        Contributor. You hereby agree to indemnify the Initial Developer
+        and every Contributor for any liability incurred by the Initial
+        Developer or such Contributor as a result of any such terms You
+        offer.
+
+        3.6. Larger Works.
+
+        You may create a Larger Work by combining Covered Software with
+        other code not governed by the terms of this License and distribute
+        the Larger Work as a single product. In such a case, You must make
+        sure the requirements of this License are fulfilled for the Covered
+        Software.
+
+    4. Versions of the License.
+        4.1. New Versions.
+
+        Sun Microsystems, Inc. is the initial license steward and may
+        publish revised and/or new versions of this License from time to
+        time. Each version will be given a distinguishing version
+        number. Except as provided in Section 4.3, no one other than the
+        license steward has the right to modify this License.
+
+        4.2. Effect of New Versions.
+
+        You may always continue to use, distribute or otherwise make the
+        Covered Software available under the terms of the version of the
+        License under which You originally received the Covered
+        Software. If the Initial Developer includes a notice in the
+        Original Software prohibiting it from being distributed or
+        otherwise made available under any subsequent version of the
+        License, You must distribute and make the Covered Software
+        available under the terms of the version of the License under which
+        You originally received the Covered Software. Otherwise, You may
+        also choose to use, distribute or otherwise make the Covered
+        Software available under the terms of any subsequent version of the
+        License published by the license steward.
+
+        4.3. Modified Versions.
+
+        When You are an Initial Developer and You want to create a new
+        license for Your Original Software, You may create and use a
+        modified version of this License if You: (a) rename the license and
+        remove any references to the name of the license steward (except to
+        note that the license differs from this License); and (b) otherwise
+        make it clear that the license contains terms which differ from
+        this License.
+
+    5. DISCLAIMER OF WARRANTY.
+
+    COVERED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS,
+    WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING,
+    WITHOUT LIMITATION, WARRANTIES THAT THE COVERED SOFTWARE IS FREE OF
+    DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR
+    NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF
+    THE COVERED SOFTWARE IS WITH YOU. SHOULD ANY COVERED SOFTWARE PROVE
+    DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER
+    CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR
+    CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART
+    OF THIS LICENSE. NO USE OF ANY COVERED SOFTWARE IS AUTHORIZED HEREUNDER
+    EXCEPT UNDER THIS DISCLAIMER.
+
+    6. TERMINATION.
+
+        6.1. This License and the rights granted hereunder will terminate
+        automatically if You fail to comply with terms herein and fail to
+        cure such breach within 30 days of becoming aware of the
+        breach. Provisions which, by their nature, must remain in effect
+        beyond the termination of this License shall survive.
+
+        6.2. If You assert a patent infringement claim (excluding
+        declaratory judgment actions) against Initial Developer or a
+        Contributor (the Initial Developer or Contributor against whom You
+        assert such claim is referred to as "Participant") alleging that
+        the Participant Software (meaning the Contributor Version where the
+        Participant is a Contributor or the Original Software where the
+        Participant is the Initial Developer) directly or indirectly
+        infringes any patent, then any and all rights granted directly or
+        indirectly to You by such Participant, the Initial Developer (if
+        the Initial Developer is not the Participant) and all Contributors
+        under Sections 2.1 and/or 2.2 of this License shall, upon 60 days
+        notice from Participant terminate prospectively and automatically
+        at the expiration of such 60 day notice period, unless if within
+        such 60 day period You withdraw Your claim with respect to the
+        Participant Software against such Participant either unilaterally
+        or pursuant to a written agreement with Participant.
+
+        6.3. In the event of termination under Sections 6.1 or 6.2 above,
+        all end user licenses that have been validly granted by You or any
+        distributor hereunder prior to termination (excluding licenses
+        granted to You by any distributor) shall survive termination.
+
+    7. LIMITATION OF LIABILITY.
+
+    UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT
+    (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL
+    DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED
+    SOFTWARE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY
+    PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
+    OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOST
+    PROFITS, LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR
+    MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF
+    SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH
+    DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR
+    DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE
+    EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO
+    NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL
+    DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.
+
+    8. U.S. GOVERNMENT END USERS.
+
+    The Covered Software is a "commercial item," as that term is defined in
+    48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer
+    software" (as that term is defined at 48 C.F.R. § 252.227-7014(a)(1))
+    and "commercial computer software documentation" as such terms are used
+    in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 C.F.R. 12.212 and
+    48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all
+    U.S. Government End Users acquire Covered Software with only those
+    rights set forth herein. This U.S. Government Rights clause is in lieu
+    of, and supersedes, any other FAR, DFAR, or other clause or provision
+    that addresses Government rights in computer software under this
+    License.
+
+    9. MISCELLANEOUS.
+
+    This License represents the complete agreement concerning subject
+    matter hereof. If any provision of this License is held to be
+    unenforceable, such provision shall be reformed only to the extent
+    necessary to make it enforceable. This License shall be governed by the
+    law of the jurisdiction specified in a notice contained within the
+    Original Software (except to the extent applicable law, if any,
+    provides otherwise), excluding such jurisdiction's conflict-of-law
+    provisions. Any litigation relating to this License shall be subject to
+    the jurisdiction of the courts located in the jurisdiction and venue
+    specified in a notice contained within the Original Software, with the
+    losing party responsible for costs, including, without limitation,
+    court costs and reasonable attorneys' fees and expenses. The
+    application of the United Nations Convention on Contracts for the
+    International Sale of Goods is expressly excluded. Any law or
+    regulation which provides that the language of a contract shall be
+    construed against the drafter shall not apply to this License. You
+    agree that You alone are responsible for compliance with the United
+    States export administration regulations (and the export control laws
+    and regulation of any other countries) when You use, distribute or
+    otherwise make available any Covered Software.
+
+    10. RESPONSIBILITY FOR CLAIMS.
+
+    As between Initial Developer and the Contributors, each party is
+    responsible for claims and damages arising, directly or indirectly, out
+    of its utilization of rights under this License and You agree to work
+    with Initial Developer and Contributors to distribute such
+    responsibility on an equitable basis. Nothing herein is intended or
+    shall be deemed to constitute any admission of liability.

Re: [patch 6/9] LICENSES: Add CDDL-1.0 license text

[Greg Kroah-Hartman]

On Mon, Apr 23, 2018 at 12:02:14AM +0200, Thomas Gleixner wrote:
> Add the full text of the CDDL-1.0 to the kernel tree.  It was copied directly
> from:
>     
>    https://spdx.org/licenses/CDDL-1.0.html#licenseText
> 
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>

Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

[patch 7/9] LICENSES: Add Apache 2.0 license text

[Thomas Gleixner]

[-- Attachment #1: LICENSES--Add-Apache-2.0-license-text.patch --]
[-- Type: text/plain, Size: 10388 bytes --]

Add the full text of the Apache License version 2 to the kernel tree.  It
was copied directly from:
    
   https://spdx.org/licenses/Apache-2.0.html#licenseText

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
 LICENSES/other/Apache-2.0 |  183 ++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 183 insertions(+)

--- /dev/null
+++ b/LICENSES/other/Apache-2.0
@@ -0,0 +1,183 @@
+Valid-License-Identifier: Apache-2.0
+SPDX-URL: https://spdx.org/licenses/Apache-2.0.html
+Usage-Guide:
+  To use the Apache License version 2.0 put the following SPDX tag/value
+  pair into a comment according to the placement guidelines in the
+  licensing rules documentation:
+    SPDX-License-Identifier: Apache-2.0
+License-Text:
+
+Apache License
+
+Version 2.0, January 2004
+
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction, and
+distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by the
+copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all other
+entities that control, are controlled by, or are under common control with
+that entity. For the purposes of this definition, "control" means (i) the
+power, direct or indirect, to cause the direction or management of such
+entity, whether by contract or otherwise, or (ii) ownership of fifty
+percent (50%) or more of the outstanding shares, or (iii) beneficial
+ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity exercising
+permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications,
+including but not limited to software source code, documentation source,
+and configuration files.
+
+"Object" form shall mean any form resulting from mechanical transformation
+or translation of a Source form, including but not limited to compiled
+object code, generated documentation, and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or Object form,
+made available under the License, as indicated by a copyright notice that
+is included in or attached to the work (an example is provided in the
+Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object form,
+that is based on (or derived from) the Work and for which the editorial
+revisions, annotations, elaborations, or other modifications represent, as
+a whole, an original work of authorship. For the purposes of this License,
+Derivative Works shall not include works that remain separable from, or
+merely link (or bind by name) to the interfaces of, the Work and Derivative
+Works thereof.
+
+"Contribution" shall mean any work of authorship, including the original
+version of the Work and any modifications or additions to that Work or
+Derivative Works thereof, that is intentionally submitted to Licensor for
+inclusion in the Work by the copyright owner or by an individual or Legal
+Entity authorized to submit on behalf of the copyright owner. For the
+purposes of this definition, "submitted" means any form of electronic,
+verbal, or written communication sent to the Licensor or its
+representatives, including but not limited to communication on electronic
+mailing lists, source code control systems, and issue tracking systems that
+are managed by, or on behalf of, the Licensor for the purpose of discussing
+and improving the Work, but excluding communication that is conspicuously
+marked or otherwise designated in writing by the copyright owner as "Not a
+Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity on
+behalf of whom a Contribution has been received by Licensor and
+subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of this
+   License, each Contributor hereby grants to You a perpetual, worldwide,
+   non-exclusive, no-charge, royalty-free, irrevocable copyright license to
+   reproduce, prepare Derivative Works of, publicly display, publicly
+   perform, sublicense, and distribute the Work and such Derivative Works
+   in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of this
+   License, each Contributor hereby grants to You a perpetual, worldwide,
+   non-exclusive, no-charge, royalty-free, irrevocable (except as stated in
+   this section) patent license to make, have made, use, offer to sell,
+   sell, import, and otherwise transfer the Work, where such license
+   applies only to those patent claims licensable by such Contributor that
+   are necessarily infringed by their Contribution(s) alone or by
+   combination of their Contribution(s) with the Work to which such
+   Contribution(s) was submitted. If You institute patent litigation
+   against any entity (including a cross-claim or counterclaim in a
+   lawsuit) alleging that the Work or a Contribution incorporated within
+   the Work constitutes direct or contributory patent infringement, then
+   any patent licenses granted to You under this License for that Work
+   shall terminate as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the Work or
+   Derivative Works thereof in any medium, with or without modifications,
+   and in Source or Object form, provided that You meet the following
+   conditions:
+
+   a. You must give any other recipients of the Work or Derivative Works a
+      copy of this License; and
+
+   b. You must cause any modified files to carry prominent notices stating
+      that You changed the files; and
+
+   c. You must retain, in the Source form of any Derivative Works that You
+      distribute, all copyright, patent, trademark, and attribution notices
+      from the Source form of the Work, excluding those notices that do not
+      pertain to any part of the Derivative Works; and
+
+   d. If the Work includes a "NOTICE" text file as part of its
+      distribution, then any Derivative Works that You distribute must
+      include a readable copy of the attribution notices contained within
+      such NOTICE file, excluding those notices that do not pertain to any
+      part of the Derivative Works, in at least one of the following
+      places: within a NOTICE text file distributed as part of the
+      Derivative Works; within the Source form or documentation, if
+      provided along with the Derivative Works; or, within a display
+      generated by the Derivative Works, if and wherever such third-party
+      notices normally appear. The contents of the NOTICE file are for
+      informational purposes only and do not modify the License. You may
+      add Your own attribution notices within Derivative Works that You
+      distribute, alongside or as an addendum to the NOTICE text from the
+      Work, provided that such additional attribution notices cannot be
+      construed as modifying the License.
+
+    You may add Your own copyright statement to Your modifications and may
+    provide additional or different license terms and conditions for use,
+    reproduction, or distribution of Your modifications, or for any such
+    Derivative Works as a whole, provided Your use, reproduction, and
+    distribution of the Work otherwise complies with the conditions stated
+    in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise, any
+   Contribution intentionally submitted for inclusion in the Work by You to
+   the Licensor shall be under the terms and conditions of this License,
+   without any additional terms or conditions. Notwithstanding the above,
+   nothing herein shall supersede or modify the terms of any separate
+   license agreement you may have executed with Licensor regarding such
+   Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or agreed to
+   in writing, Licensor provides the Work (and each Contributor provides
+   its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS
+   OF ANY KIND, either express or implied, including, without limitation,
+   any warranties or conditions of TITLE, NON-INFRINGEMENT,
+   MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely
+   responsible for determining the appropriateness of using or
+   redistributing the Work and assume any risks associated with Your
+   exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory, whether
+   in tort (including negligence), contract, or otherwise, unless required
+   by applicable law (such as deliberate and grossly negligent acts) or
+   agreed to in writing, shall any Contributor be liable to You for
+   damages, including any direct, indirect, special, incidental, or
+   consequential damages of any character arising as a result of this
+   License or out of the use or inability to use the Work (including but
+   not limited to damages for loss of goodwill, work stoppage, computer
+   failure or malfunction, or any and all other commercial damages or
+   losses), even if such Contributor has been advised of the possibility of
+   such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing the
+   Work or Derivative Works thereof, You may choose to offer, and charge a
+   fee for, acceptance of support, warranty, indemnity, or other liability
+   obligations and/or rights consistent with this License. However, in
+   accepting such obligations, You may act only on Your own behalf and on
+   Your sole responsibility, not on behalf of any other Contributor, and
+   only if You agree to indemnify, defend, and hold each Contributor
+   harmless for any liability incurred by, or claims asserted against, such
+   Contributor by reason of your accepting any such warranty or additional
+   liability.
+
+END OF TERMS AND CONDITIONS

Re: [patch 7/9] LICENSES: Add Apache 2.0 license text

[Greg Kroah-Hartman]

On Mon, Apr 23, 2018 at 12:02:15AM +0200, Thomas Gleixner wrote:
> Add the full text of the Apache License version 2 to the kernel tree.  It
> was copied directly from:
>     
>    https://spdx.org/licenses/Apache-2.0.html#licenseText
> 
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>

Ugh, blame Android for this one :(

Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

[patch 8/9] LICENSES: Add CC-BY-SA-4.0 license text

[Thomas Gleixner]

[-- Attachment #1: LICENSES--Add-CC-BY-SA-4.0-license-text.patch --]
[-- Type: text/plain, Size: 21147 bytes --]

Add the full text of the CC-BY-SA-4.0 license to the kernel tree.  It was
copied directly from:
    
   https://spdx.org/licenses/CC-BY-SA-4.0.html#licenseText

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
 LICENSES/other/CC-BY-SA-4.0 |  397 ++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 397 insertions(+)

--- /dev/null
+++ b/LICENSES/other/CC-BY-SA-4.0
@@ -0,0 +1,397 @@
+Valid-License-Identifier: CC-BY-SA-4.0
+SPDX-URL: https://spdx.org/licenses/CC-BY-SA-4.0
+Usage-Guide:
+  To use the Creative Commons Attribution Share Alike 4.0 International
+  license put the following SPDX tag/value pair into a comment according to
+  the placement guidelines in the licensing rules documentation:
+    SPDX-License-Identifier: CC-BY-SA-4.0
+License-Text:
+
+Creative Commons Attribution-ShareAlike 4.0 International
+
+Creative Commons Corporation ("Creative Commons") is not a law firm and
+does not provide legal services or legal advice. Distribution of Creative
+Commons public licenses does not create a lawyer-client or other
+relationship. Creative Commons makes its licenses and related information
+available on an "as-is" basis. Creative Commons gives no warranties
+regarding its licenses, any material licensed under their terms and
+conditions, or any related information. Creative Commons disclaims all
+liability for damages resulting from their use to the fullest extent
+possible.
+
+Using Creative Commons Public Licenses
+
+Creative Commons public licenses provide a standard set of terms and
+conditions that creators and other rights holders may use to share original
+works of authorship and other material subject to copyright and certain
+other rights specified in the public license below. The following
+considerations are for informational purposes only, are not exhaustive, and
+do not form part of our licenses.
+
+Considerations for licensors: Our public licenses are intended for use by
+those authorized to give the public permission to use material in ways
+otherwise restricted by copyright and certain other rights. Our licenses
+are irrevocable. Licensors should read and understand the terms and
+conditions of the license they choose before applying it. Licensors should
+also secure all rights necessary before applying our licenses so that the
+public can reuse the material as expected. Licensors should clearly mark
+any material not subject to the license. This includes other CC-licensed
+material, or material used under an exception or limitation to
+copyright. More considerations for licensors :
+wiki.creativecommons.org/Considerations_for_licensors
+
+Considerations for the public: By using one of our public licenses, a
+licensor grants the public permission to use the licensed material under
+specified terms and conditions. If the licensor's permission is not
+necessary for any reason–for example, because of any applicable exception
+or limitation to copyright–then that use is not regulated by the
+license. Our licenses grant only permissions under copyright and certain
+other rights that a licensor has authority to grant. Use of the licensed
+material may still be restricted for other reasons, including because
+others have copyright or other rights in the material. A licensor may make
+special requests, such as asking that all changes be marked or described.
+
+Although not required by our licenses, you are encouraged to respect those
+requests where reasonable. More considerations for the public :
+wiki.creativecommons.org/Considerations_for_licensees
+
+Creative Commons Attribution-ShareAlike 4.0 International Public License
+
+By exercising the Licensed Rights (defined below), You accept and agree to
+be bound by the terms and conditions of this Creative Commons
+Attribution-ShareAlike 4.0 International Public License ("Public
+License"). To the extent this Public License may be interpreted as a
+contract, You are granted the Licensed Rights in consideration of Your
+acceptance of these terms and conditions, and the Licensor grants You such
+rights in consideration of benefits the Licensor receives from making the
+Licensed Material available under these terms and conditions.
+
+Section 1 – Definitions.
+
+    a. Adapted Material means material subject to Copyright and Similar
+       Rights that is derived from or based upon the Licensed Material and
+       in which the Licensed Material is translated, altered, arranged,
+       transformed, or otherwise modified in a manner requiring permission
+       under the Copyright and Similar Rights held by the Licensor. For
+       purposes of this Public License, where the Licensed Material is a
+       musical work, performance, or sound recording, Adapted Material is
+       always produced where the Licensed Material is synched in timed
+       relation with a moving image.
+
+    b. Adapter's License means the license You apply to Your Copyright and
+       Similar Rights in Your contributions to Adapted Material in
+       accordance with the terms and conditions of this Public License.
+
+    c. BY-SA Compatible License means a license listed at
+       creativecommons.org/compatiblelicenses, approved by Creative Commons
+       as essentially the equivalent of this Public License.
+
+    d. Copyright and Similar Rights means copyright and/or similar rights
+       closely related to copyright including, without limitation,
+       performance, broadcast, sound recording, and Sui Generis Database
+       Rights, without regard to how the rights are labeled or
+       categorized. For purposes of this Public License, the rights
+       specified in Section 2(b)(1)-(2) are not Copyright and Similar
+       Rights.
+
+    e. Effective Technological Measures means those measures that, in the
+       absence of proper authority, may not be circumvented under laws
+       fulfilling obligations under Article 11 of the WIPO Copyright Treaty
+       adopted on December 20, 1996, and/or similar international
+       agreements.
+
+    f. Exceptions and Limitations means fair use, fair dealing, and/or any
+       other exception or limitation to Copyright and Similar Rights that
+       applies to Your use of the Licensed Material.
+
+    g. License Elements means the license attributes listed in the name of
+       a Creative Commons Public License. The License Elements of this
+       Public License are Attribution and ShareAlike.
+
+    h. Licensed Material means the artistic or literary work, database, or
+       other material to which the Licensor applied this Public License.
+
+    i. Licensed Rights means the rights granted to You subject to the terms
+       and conditions of this Public License, which are limited to all
+       Copyright and Similar Rights that apply to Your use of the Licensed
+       Material and that the Licensor has authority to license.
+
+    j. Licensor means the individual(s) or entity(ies) granting rights
+       under this Public License.
+
+    k. Share means to provide material to the public by any means or
+       process that requires permission under the Licensed Rights, such as
+       reproduction, public display, public performance, distribution,
+       dissemination, communication, or importation, and to make material
+       available to the public including in ways that members of the public
+       may access the material from a place and at a time individually
+       chosen by them.
+
+    l. Sui Generis Database Rights means rights other than copyright
+       resulting from Directive 96/9/EC of the European Parliament and of
+       the Council of 11 March 1996 on the legal protection of databases,
+       as amended and/or succeeded, as well as other essentially equivalent
+       rights anywhere in the world.  m. You means the individual or entity
+       exercising the Licensed Rights under this Public License. Your has a
+       corresponding meaning.
+
+Section 2 – Scope.
+
+    a. License grant.
+
+        1. Subject to the terms and conditions of this Public License, the
+           Licensor hereby grants You a worldwide, royalty-free,
+           non-sublicensable, non-exclusive, irrevocable license to
+           exercise the Licensed Rights in the Licensed Material to:
+
+            A. reproduce and Share the Licensed Material, in whole or in part; and
+
+            B. produce, reproduce, and Share Adapted Material.
+
+        2. Exceptions and Limitations. For the avoidance of doubt, where
+           Exceptions and Limitations apply to Your use, this Public
+           License does not apply, and You do not need to comply with its
+           terms and conditions.
+
+        3. Term. The term of this Public License is specified in Section 6(a).
+
+        4. Media and formats; technical modifications allowed. The Licensor
+       	   authorizes You to exercise the Licensed Rights in all media and
+       	   formats whether now known or hereafter created, and to make
+       	   technical modifications necessary to do so. The Licensor waives
+       	   and/or agrees not to assert any right or authority to forbid You
+       	   from making technical modifications necessary to exercise the
+       	   Licensed Rights, including technical modifications necessary to
+       	   circumvent Effective Technological Measures. For purposes of
+       	   this Public License, simply making modifications authorized by
+       	   this Section 2(a)(4) never produces Adapted Material.
+
+        5. Downstream recipients.
+
+            A. Offer from the Licensor – Licensed Material. Every recipient
+               of the Licensed Material automatically receives an offer
+               from the Licensor to exercise the Licensed Rights under the
+               terms and conditions of this Public License.
+
+            B. Additional offer from the Licensor – Adapted Material. Every
+               recipient of Adapted Material from You automatically
+               receives an offer from the Licensor to exercise the Licensed
+               Rights in the Adapted Material under the conditions of the
+               Adapter's License You apply.
+
+            C. No downstream restrictions. You may not offer or impose any
+               additional or different terms or conditions on, or apply any
+               Effective Technological Measures to, the Licensed Material
+               if doing so restricts exercise of the Licensed Rights by any
+               recipient of the Licensed Material.
+
+        6. No endorsement. Nothing in this Public License constitutes or
+           may be construed as permission to assert or imply that You are,
+           or that Your use of the Licensed Material is, connected with, or
+           sponsored, endorsed, or granted official status by, the Licensor
+           or others designated to receive attribution as provided in
+           Section 3(a)(1)(A)(i).
+
+    b. Other rights.
+
+        1. Moral rights, such as the right of integrity, are not licensed
+           under this Public License, nor are publicity, privacy, and/or
+           other similar personality rights; however, to the extent
+           possible, the Licensor waives and/or agrees not to assert any
+           such rights held by the Licensor to the limited extent necessary
+           to allow You to exercise the Licensed Rights, but not otherwise.
+
+        2. Patent and trademark rights are not licensed under this Public
+           License.
+
+        3. To the extent possible, the Licensor waives any right to collect
+           royalties from You for the exercise of the Licensed Rights,
+           whether directly or through a collecting society under any
+           voluntary or waivable statutory or compulsory licensing
+           scheme. In all other cases the Licensor expressly reserves any
+           right to collect such royalties.
+
+Section 3 – License Conditions.
+
+Your exercise of the Licensed Rights is expressly made subject to the
+following conditions.
+
+    a. Attribution.
+
+        1. If You Share the Licensed Material (including in modified form),
+           You must:
+
+            A. retain the following if it is supplied by the Licensor with
+               the Licensed Material:
+
+                i. identification of the creator(s) of the Licensed
+                   Material and any others designated to receive
+                   attribution, in any reasonable manner requested by the
+                   Licensor (including by pseudonym if designated);
+
+                ii. a copyright notice;
+
+                iii. a notice that refers to this Public License;
+
+                iv. a notice that refers to the disclaimer of warranties;
+
+                v. a URI or hyperlink to the Licensed Material to the extent reasonably practicable;
+
+            B. indicate if You modified the Licensed Material and retain an
+               indication of any previous modifications; and
+
+            C. indicate the Licensed Material is licensed under this Public
+            License, and include the text of, or the URI or hyperlink to,
+            this Public License.
+
+        2. You may satisfy the conditions in Section 3(a)(1) in any
+           reasonable manner based on the medium, means, and context in
+           which You Share the Licensed Material. For example, it may be
+           reasonable to satisfy the conditions by providing a URI or
+           hyperlink to a resource that includes the required information.
+
+        3. If requested by the Licensor, You must remove any of the
+    	   information required by Section 3(a)(1)(A) to the extent
+    	   reasonably practicable.  b. ShareAlike.In addition to the
+    	   conditions in Section 3(a), if You Share Adapted Material You
+    	   produce, the following conditions also apply.
+
+           1. The Adapter's License You apply must be a Creative Commons
+              license with the same License Elements, this version or
+              later, or a BY-SA Compatible License.
+
+           2. You must include the text of, or the URI or hyperlink to, the
+              Adapter's License You apply. You may satisfy this condition
+              in any reasonable manner based on the medium, means, and
+              context in which You Share Adapted Material.
+
+           3. You may not offer or impose any additional or different terms
+              or conditions on, or apply any Effective Technological
+              Measures to, Adapted Material that restrict exercise of the
+              rights granted under the Adapter's License You apply.
+
+Section 4 – Sui Generis Database Rights.
+
+Where the Licensed Rights include Sui Generis Database Rights that apply to
+Your use of the Licensed Material:
+
+    a. for the avoidance of doubt, Section 2(a)(1) grants You the right to
+       extract, reuse, reproduce, and Share all or a substantial portion of
+       the contents of the database;
+
+    b. if You include all or a substantial portion of the database contents
+       in a database in which You have Sui Generis Database Rights, then
+       the database in which You have Sui Generis Database Rights (but not
+       its individual contents) is Adapted Material, including for purposes
+       of Section 3(b); and
+
+    c. You must comply with the conditions in Section 3(a) if You Share all
+       or a substantial portion of the contents of the database.
+
+    For the avoidance of doubt, this Section 4 supplements and does not
+    replace Your obligations under this Public License where the Licensed
+    Rights include other Copyright and Similar Rights.
+
+Section 5 – Disclaimer of Warranties and Limitation of Liability.
+
+    a. Unless otherwise separately undertaken by the Licensor, to the
+       extent possible, the Licensor offers the Licensed Material as-is and
+       as-available, and makes no representations or warranties of any kind
+       concerning the Licensed Material, whether express, implied,
+       statutory, or other. This includes, without limitation, warranties
+       of title, merchantability, fitness for a particular purpose,
+       non-infringement, absence of latent or other defects, accuracy, or
+       the presence or absence of errors, whether or not known or
+       discoverable. Where disclaimers of warranties are not allowed in
+       full or in part, this disclaimer may not apply to You.
+
+    b. To the extent possible, in no event will the Licensor be liable to
+       You on any legal theory (including, without limitation, negligence)
+       or otherwise for any direct, special, indirect, incidental,
+       consequential, punitive, exemplary, or other losses, costs,
+       expenses, or damages arising out of this Public License or use of
+       the Licensed Material, even if the Licensor has been advised of the
+       possibility of such losses, costs, expenses, or damages. Where a
+       limitation of liability is not allowed in full or in part, this
+       limitation may not apply to You.
+
+    c. The disclaimer of warranties and limitation of liability provided
+       above shall be interpreted in a manner that, to the extent possible,
+       most closely approximates an absolute disclaimer and waiver of all
+       liability.
+
+Section 6 – Term and Termination.
+
+    a. This Public License applies for the term of the Copyright and
+       Similar Rights licensed here. However, if You fail to comply with
+       this Public License, then Your rights under this Public License
+       terminate automatically.
+
+    b. Where Your right to use the Licensed Material has terminated under
+       Section 6(a), it reinstates:
+
+        1. automatically as of the date the violation is cured, provided it
+           is cured within 30 days of Your discovery of the violation; or
+
+        2. upon express reinstatement by the Licensor.
+
+    c. For the avoidance of doubt, this Section 6(b) does not affect any
+       right the Licensor may have to seek remedies for Your violations of
+       this Public License.
+
+    d. For the avoidance of doubt, the Licensor may also offer the Licensed
+       Material under separate terms or conditions or stop distributing the
+       Licensed Material at any time; however, doing so will not terminate
+       this Public License.
+
+    e. Sections 1, 5, 6, 7, and 8 survive termination of this Public License.
+
+Section 7 – Other Terms and Conditions.
+
+    a. The Licensor shall not be bound by any additional or different terms
+       or conditions communicated by You unless expressly agreed.
+
+    b. Any arrangements, understandings, or agreements regarding the
+       Licensed Material not stated herein are separate from and
+       independent of the terms and conditions of this Public License.
+
+Section 8 – Interpretation.
+
+    a. For the avoidance of doubt, this Public License does not, and shall
+       not be interpreted to, reduce, limit, restrict, or impose conditions
+       on any use of the Licensed Material that could lawfully be made
+       without permission under this Public License.
+
+    b. To the extent possible, if any provision of this Public License is
+       deemed unenforceable, it shall be automatically reformed to the
+       minimum extent necessary to make it enforceable. If the provision
+       cannot be reformed, it shall be severed from this Public License
+       without affecting the enforceability of the remaining terms and
+       conditions.
+
+    c. No term or condition of this Public License will be waived and no
+       failure to comply consented to unless expressly agreed to by the
+       Licensor.
+
+    d. Nothing in this Public License constitutes or may be interpreted as
+       a limitation upon, or waiver of, any privileges and immunities that
+       apply to the Licensor or You, including from the legal processes of
+       any jurisdiction or authority.
+
+Creative Commons is not a party to its public licenses. Notwithstanding,
+Creative Commons may elect to apply one of its public licenses to material
+it publishes and in those instances will be considered the "Licensor." The
+text of the Creative Commons public licenses is dedicated to the public
+domain under the CC0 Public Domain Dedication. Except for the limited
+purpose of indicating that material is shared under a Creative Commons
+public license or as otherwise permitted by the Creative Commons policies
+published at creativecommons.org/policies, Creative Commons does not
+authorize the use of the trademark "Creative Commons" or any other
+trademark or logo of Creative Commons without its prior written consent
+including, without limitation, in connection with any unauthorized
+modifications to any of its public licenses or any other arrangements,
+understandings, or agreements concerning use of licensed material. For the
+avoidance of doubt, this paragraph does not form part of the public
+licenses.
+
+Creative Commons may be contacted at creativecommons.org.

Re: [patch 8/9] LICENSES: Add CC-BY-SA-4.0 license text

[Greg Kroah-Hartman]

On Mon, Apr 23, 2018 at 12:02:16AM +0200, Thomas Gleixner wrote:
> Add the full text of the CC-BY-SA-4.0 license to the kernel tree.  It was
> copied directly from:
>     
>    https://spdx.org/licenses/CC-BY-SA-4.0.html#licenseText
> 
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>

As we only have 1 user of this, do we really need it?

Willy, it's your file, Documentation/core-api/idr.rst that is needing
this addition to the LICENSES directory.  While I'm all for CC licenses
for Documentation, we don't seem to be very consistent with them.
Should this be the "default" license we choose for documentation for now
on?

thanks,

greg k-h

Re: [patch 8/9] LICENSES: Add CC-BY-SA-4.0 license text

[Thomas Gleixner]

On Mon, 23 Apr 2018, Greg Kroah-Hartman wrote:
> On Mon, Apr 23, 2018 at 12:02:16AM +0200, Thomas Gleixner wrote:
> > Add the full text of the CC-BY-SA-4.0 license to the kernel tree.  It was
> > copied directly from:
> >     
> >    https://spdx.org/licenses/CC-BY-SA-4.0.html#licenseText
> > 
> > Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> 
> As we only have 1 user of this, do we really need it?
> 
> Willy, it's your file, Documentation/core-api/idr.rst that is needing
> this addition to the LICENSES directory.  While I'm all for CC licenses
> for Documentation, we don't seem to be very consistent with them.
> Should this be the "default" license we choose for documentation for now
> on?

I'm all for it. If we can agree than this should move to preferred/ and not
to other/

Thanks,

	tglx

Re: [patch 8/9] LICENSES: Add CC-BY-SA-4.0 license text

[Greg Kroah-Hartman]

On Mon, Apr 23, 2018 at 09:37:14AM +0200, Thomas Gleixner wrote:
> On Mon, 23 Apr 2018, Greg Kroah-Hartman wrote:
> > On Mon, Apr 23, 2018 at 12:02:16AM +0200, Thomas Gleixner wrote:
> > > Add the full text of the CC-BY-SA-4.0 license to the kernel tree.  It was
> > > copied directly from:
> > >     
> > >    https://spdx.org/licenses/CC-BY-SA-4.0.html#licenseText
> > > 
> > > Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> > 
> > As we only have 1 user of this, do we really need it?
> > 
> > Willy, it's your file, Documentation/core-api/idr.rst that is needing
> > this addition to the LICENSES directory.  While I'm all for CC licenses
> > for Documentation, we don't seem to be very consistent with them.
> > Should this be the "default" license we choose for documentation for now
> > on?
> 
> I'm all for it. If we can agree than this should move to preferred/ and not
> to other/

Ok, that sounds good, Jon?  I know you have looked into picking a decent
license for documentation, any thoughts here?

thanks,

greg k-h

Re: [patch 8/9] LICENSES: Add CC-BY-SA-4.0 license text

[Mauro Carvalho Chehab]

Em Mon, 23 Apr 2018 10:26:35 +0200
Greg Kroah-Hartman <gregkh@linuxfoundation.org> escreveu:

> On Mon, Apr 23, 2018 at 09:37:14AM +0200, Thomas Gleixner wrote:
> > On Mon, 23 Apr 2018, Greg Kroah-Hartman wrote:  
> > > On Mon, Apr 23, 2018 at 12:02:16AM +0200, Thomas Gleixner wrote:  
> > > > Add the full text of the CC-BY-SA-4.0 license to the kernel tree.  It was
> > > > copied directly from:
> > > >     
> > > >    https://spdx.org/licenses/CC-BY-SA-4.0.html#licenseText
> > > > 
> > > > Signed-off-by: Thomas Gleixner <tglx@linutronix.de>  
> > > 
> > > As we only have 1 user of this, do we really need it?
> > > 
> > > Willy, it's your file, Documentation/core-api/idr.rst that is needing
> > > this addition to the LICENSES directory.  While I'm all for CC licenses
> > > for Documentation, we don't seem to be very consistent with them.
> > > Should this be the "default" license we choose for documentation for now
> > > on?  
> > 
> > I'm all for it. If we can agree than this should move to preferred/ and not
> > to other/  
> 
> Ok, that sounds good, Jon?  I know you have looked into picking a decent
> license for documentation, any thoughts here?

My 2 cents here: I'm a big fan of using C-BY-SA-4.0 for documentation.
IMO, it fits better than GPL for docs. For a pure .rst file that doesn't
use kernel-doc, that is the best choice on my PoV.

Yet, I'm not sure if we can import something from a GPL (using kernel-docs)
on a CC rst file. Perhaps it needs some exemption to explicitly allow that.

Thanks,
Mauro

Re: [patch 8/9] LICENSES: Add CC-BY-SA-4.0 license text

[Jonathan Corbet]

On Mon, 23 Apr 2018 10:26:35 +0200
Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:

> > > Willy, it's your file, Documentation/core-api/idr.rst that is needing
> > > this addition to the LICENSES directory.  While I'm all for CC licenses
> > > for Documentation, we don't seem to be very consistent with them.
> > > Should this be the "default" license we choose for documentation for now
> > > on?  
> > 
> > I'm all for it. If we can agree than this should move to preferred/ and not
> > to other/  
> 
> Ok, that sounds good, Jon?  I know you have looked into picking a decent
> license for documentation, any thoughts here?

CC-BY-SA is a good license for docs, but it's not GPL-compatible, so I
don't think that anything with that license can incorporate kerneldoc
comments or, conceivably, be integrated into the whole sphinx document
tree (which does use those comments).  That leads to my own believe that
the docs really need to be GPL-licensed, even though it's not the ideal
solution.

I suppose it might be worth putting this question to the LF lawyers to
see what they think.  It's not as if I really know what I'm talking
about, after all...

jon

[patch 9/9] LICENSES: Add Linux-OpenIB license text

[Thomas Gleixner]

[-- Attachment #1: LICENSES--Add-Linux-OpenIB-license-text.patch --]
[-- Type: text/plain, Size: 1932 bytes --]

The infiniband code uses a variant of the OpenIB license. This license is
BSD-2-Clause with the MIT disclaimer. The linux kernel uses this license
extensively throughout the driver subsystem since 2005. Note that the
OpenIB.org license is a true match to BSD-2-Clause.

The license text was copied from:

    https://spdx.org/licenses/Linux-OpenIB.html#licenseText

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
 LICENSES/other/Linux-OpenIB |   26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)

--- /dev/null
+++ b/LICENSES/other/Linux-OpenIB
@@ -0,0 +1,26 @@
+Valid-License-Identifier: Linux-OpenIB
+SPDX-URL: https://spdx.org/licenses/Linux-OpenIB.html
+Usage-Guide:
+  To use the Linux Kernel Variant of OpenIB.org license put the following
+  SPDX tag/value pair into a comment according to the placement guidelines
+  in the licensing rules documentation:
+    SPDX-License-Identifier: Linux-OpenIB
+License-Text:
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+    - Redistributions of source code must retain the above copyright
+      notice, this list of conditions and the following disclaimer.
+    
+    - Redistributions in binary form must reproduce the above copyright
+      notice, this list of conditions and the following disclaimer in the
+      documentation and/or other materials provided with the distribution.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+DEALINGS IN THE SOFTWARE.

Re: [patch 9/9] LICENSES: Add Linux-OpenIB license text

[Greg Kroah-Hartman]

On Mon, Apr 23, 2018 at 12:02:17AM +0200, Thomas Gleixner wrote:
> The infiniband code uses a variant of the OpenIB license. This license is
> BSD-2-Clause with the MIT disclaimer. The linux kernel uses this license
> extensively throughout the driver subsystem since 2005. Note that the
> OpenIB.org license is a true match to BSD-2-Clause.
> 
> The license text was copied from:
> 
>     https://spdx.org/licenses/Linux-OpenIB.html#licenseText
> 
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>

Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Re: [patch 0/9] LICENSES: Add missing License Text and fixup bogus identifiers

[Greg Kroah-Hartman]

On Mon, Apr 23, 2018 at 12:02:08AM +0200, Thomas Gleixner wrote:
> There are a few bogus SPDX identifiers in various files and SPDX
> Identifiers used in tree or about to be used which have no corresponding
> License Text file in the LICENSES directory or use the new variant of the
> GPL-2.0[+] license identifiers which are not mentioned in the GPL-2.0
> Valid-License-Identifiers: tags.
> 
> The following series cleans that up:
> 
>  - Use the proper identifiers
> 
>  - Add GPL-2.0-only and GPL-2.0-or-later identifiers to the GPL2.0 license
> 
>  - Add X11, Apache-2.0, CC-BY-SA-4.0, CCDL-1.0, Linux-OpenIB license texts
>    to the LICENSES directory along with the required documentation texts

I'm thinking we need a script to keep these in check, right?  Does
checkpatch.pl handle knowing what the "currently good" list of license
tags are, or should we just use a separate script to parse the LICENSES/
directory to get that list?

Either way, nice work on this series, thanks for keeping up with them.

thanks,

greg k-h

Re: [patch 0/9] LICENSES: Add missing License Text and fixup bogus identifiers

[Thomas Gleixner]

On Mon, 23 Apr 2018, Greg Kroah-Hartman wrote:
> On Mon, Apr 23, 2018 at 12:02:08AM +0200, Thomas Gleixner wrote:
> > There are a few bogus SPDX identifiers in various files and SPDX
> > Identifiers used in tree or about to be used which have no corresponding
> > License Text file in the LICENSES directory or use the new variant of the
> > GPL-2.0[+] license identifiers which are not mentioned in the GPL-2.0
> > Valid-License-Identifiers: tags.
> > 
> > The following series cleans that up:
> > 
> >  - Use the proper identifiers
> > 
> >  - Add GPL-2.0-only and GPL-2.0-or-later identifiers to the GPL2.0 license
> > 
> >  - Add X11, Apache-2.0, CC-BY-SA-4.0, CCDL-1.0, Linux-OpenIB license texts
> >    to the LICENSES directory along with the required documentation texts
> 
> I'm thinking we need a script to keep these in check, right?  Does
> checkpatch.pl handle knowing what the "currently good" list of license
> tags are, or should we just use a separate script to parse the LICENSES/
> directory to get that list?

checkpatch.pl does not know about it. I have a python script which does the
parsing of the LICENSES directory and checks against every file in the
tree. I need to make that work with patches. I'm not sure whether
checkpatch.pl should grow all the parser knowledge, I guess it can just
invoke the script and be done with it.

Thanks,

	tglx