All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Christoph Hellwig <hch@infradead.org>,
	"Theodore Ts'o" <tytso@mit.edu>,
	"Darrick J. Wong" <darrick.wong@oracle.com>,
	Eric Sandeen <sandeen@redhat.com>,
	xfs <linux-xfs@vger.kernel.org>,
	Richard Fontana <fontana@sharpeleven.org>,
	linux-kernel@vger.kernel.org
Subject: Re: WTF? Re: [PATCH] License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Date: Wed, 8 Nov 2017 17:19:38 +0000	[thread overview]
Message-ID: <20171108171938.7df66c65@alans-desktop> (raw)
In-Reply-To: <20171107214259.GC16026@wotan.suse.de>

>     By default all files without license information are under the default
>     license of the kernel, which is GPL version 2.

Which is factually incorrect.

They are under a licence that is at least as permissive as GPL v2.
However they may be under a more permissive licence and as you are not
the rightsholder you don't have the right to relicence them mroe
restrictvely.

For example

I find a reference piece of code whose author says it is 'too trivial to
copyright'. I (not the author0 place that code in the kernel. The licence
on that code is still 'too trivial to copyright' (by estoppel). That's
GPL 2 compliant but it is *NOT* GPL.

As anyone can contribute third party code that is GPL compliant
legitimately you can't assume any unmarked code is GPL, merely 'at least
GPL'.

Alan

  parent reply	other threads:[~2017-11-08 17:20 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-07  2:06 [PATCH] License cleanup: add SPDX GPL-2.0 license identifier to files with no license Darrick J. Wong
2017-11-07  7:20 ` WTF? " Christoph Hellwig
2017-11-07  7:39   ` Greg Kroah-Hartman
2017-11-07 17:07     ` Alan Cox
2017-11-07 17:12       ` Greg Kroah-Hartman
2017-11-07 17:25         ` Alan Cox
2017-11-07 18:30           ` Greg Kroah-Hartman
2017-11-07 17:20     ` Darrick J. Wong
2017-11-07 18:29       ` Greg Kroah-Hartman
2017-11-07 18:46         ` Alan Cox
2017-11-07 19:15           ` Theodore Ts'o
2017-11-07 19:28             ` Christoph Hellwig
2017-11-07 20:26               ` Greg Kroah-Hartman
2017-11-07 21:42                 ` Luis R. Rodriguez
2017-11-08  6:37                   ` Greg Kroah-Hartman
2017-11-08 17:19                   ` Alan Cox [this message]
2017-11-08 18:46                 ` Darrick J. Wong
2017-11-09  8:19                   ` Greg Kroah-Hartman
2017-11-08 12:35               ` Philippe Ombredanne
2017-11-08 15:11                 ` Christoph Hellwig
2017-11-08 18:06                   ` Christoph Hellwig
2017-11-09  8:23                   ` Greg Kroah-Hartman
2017-11-09  8:53                     ` Christoph Hellwig
2017-11-22 17:07                 ` Pavel Machek
2017-11-22 17:53                   ` Greg Kroah-Hartman
2017-11-25 19:12                     ` Pavel Machek
2017-11-25 21:57                       ` Joe Perches
2017-11-27 16:50                       ` Darrick J. Wong
2017-11-22 16:19             ` Pavel Machek
2017-11-08 23:47         ` Dave Chinner
2017-11-09  8:16           ` Greg Kroah-Hartman
2017-11-10 21:10             ` Alan Cox

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=20171108171938.7df66c65@alans-desktop \
    --to=gnomes@lxorguk.ukuu.org.uk \
    --cc=darrick.wong@oracle.com \
    --cc=fontana@sharpeleven.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=sandeen@redhat.com \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is 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.