From: "Theodore Ts'o" <tytso@mit.edu>
To: Stefan Roese <sr@denx.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
monstr@monstr.eu, balbi@ti.com, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, Wolfgang Denk <wd@denx.de>
Subject: Re: SPDX-License-Identifier
Date: Wed, 4 Feb 2015 23:21:06 -0500 [thread overview]
Message-ID: <20150205042106.GK2509@thunk.org> (raw)
In-Reply-To: <54D24BA4.3070509@denx.de>
On Wed, Feb 04, 2015 at 05:41:08PM +0100, Stefan Roese wrote:
> Because of this it is really important to know the exact license(s) for each
> and every file. And they can vary very much. Here some examples:
>
> GPL v3 or later:
>
> scripts/dtc/dtc-parser.tab.c_shipped
> scripts/dtc/dtc-parser.tab.h_shipped
> scripts/kconfig/zconf.tab.c_shipped
> scripts/genksyms/parse.tab.h_shipped
> scripts/genksyms/parse.tab.c_shipped
I certainly hope the automated license clearing tools are smart enough
to distinguish random GPLv3 source files with the output of Bison
which has the additional clause:
/* As a special exception, you may create a larger work that contains
part or all of the Bison parser skeleton and distribute that work
under terms of your choice, so long as that work isn't itself a
parser generator using the skeleton or a modified version thereof
as a parser skeleton. Alternatively, if you modify or redistribute
the parser skeleton itself, you may (at your option) remove this
special exception, which will cause the skeleton and the resulting
Bison output files to be licensed under the GNU General Public
License without this special exception.
This special exception was added by the Free Software Foundation in
version 2.2 of Bison. */
Otherwise, these automated tools which general much noise that will
lead to panic-stricken legal beagles to seriously annoy the kernel
developers....
- Ted
next prev parent reply other threads:[~2015-02-05 4:21 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 9:40 [PATCH RFC] usb: gadget: Add xilinx axi usb2 device support Subbaraya Sundeep Bhatta
2014-02-20 18:23 ` Felipe Balbi
2014-02-21 6:38 ` Michal Simek
2014-02-21 16:04 ` Greg Kroah-Hartman
2014-02-21 16:04 ` Michal Simek
2014-02-21 16:12 ` SPDX-License-Identifier (was: Re: [PATCH RFC] usb: gadget: Add xilinx axi usb2 device support) Felipe Balbi
2014-02-21 16:18 ` SPDX-License-Identifier Michal Simek
2014-02-21 16:20 ` SPDX-License-Identifier Felipe Balbi
2014-02-21 16:56 ` SPDX-License-Identifier Greg Kroah-Hartman
2014-02-21 17:26 ` SPDX-License-Identifier Michal Simek
2014-02-21 17:57 ` SPDX-License-Identifier Greg Kroah-Hartman
2014-02-21 19:01 ` SPDX-License-Identifier Theodore Ts'o
2014-02-24 10:12 ` SPDX-License-Identifier Michal Simek
2014-02-24 13:41 ` SPDX-License-Identifier Theodore Ts'o
2014-02-24 14:03 ` SPDX-License-Identifier Michal Simek
2014-02-24 14:26 ` SPDX-License-Identifier Greg Kroah-Hartman
2014-02-25 12:10 ` SPDX-License-Identifier One Thousand Gnomes
2014-02-25 12:25 ` SPDX-License-Identifier Geert Uytterhoeven
2015-02-02 15:43 ` SPDX-License-Identifier Stefan Roese
2015-02-02 16:06 ` SPDX-License-Identifier Greg Kroah-Hartman
2015-02-04 16:41 ` SPDX-License-Identifier Stefan Roese
2015-02-05 4:21 ` Theodore Ts'o [this message]
2015-02-05 6:41 ` SPDX-License-Identifier Greg Kroah-Hartman
2015-02-25 21:49 ` SPDX-License-Identifier Pavel Machek
2015-02-25 22:00 ` SPDX-License-Identifier Felipe Balbi
2015-02-26 21:49 ` SPDX-License-Identifier Pavel Machek
2015-02-26 10:26 ` SPDX-License-Identifier One Thousand Gnomes
2015-02-26 13:39 ` SPDX-License-Identifier Theodore Ts'o
2015-02-26 21:53 ` SPDX-License-Identifier Pavel Machek
2015-02-05 11:49 ` SPDX-License-Identifier One Thousand Gnomes
2014-02-21 16:23 ` [PATCH RFC] usb: gadget: Add xilinx axi usb2 device support Greg Kroah-Hartman
2014-02-21 11:27 ` Subbaraya Sundeep Bhatta
2014-02-21 15:39 ` Felipe Balbi
2014-03-10 13:36 ` sundeep subbaraya
2014-03-10 18:44 ` Felipe Balbi
2014-02-21 12:04 ` Mark Rutland
2014-02-21 13:41 ` Michal Simek
2014-02-21 13:57 ` Mark Rutland
2014-02-21 14:06 ` Michal Simek
2014-02-21 15:42 ` Felipe Balbi
2014-02-21 15:51 ` Michal Simek
2014-02-21 16:00 ` Felipe Balbi
2014-02-21 16:15 ` Arnd Bergmann
2014-02-21 15:41 ` Felipe Balbi
2014-02-21 16:13 ` Mark Rutland
2014-03-26 10:07 ` sundeep subbaraya
2014-04-15 17:18 ` Felipe Balbi
2014-04-15 17:55 ` Alan Stern
2014-04-16 4:39 ` Felipe Balbi
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=20150205042106.GK2509@thunk.org \
--to=tytso@mit.edu \
--cc=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@monstr.eu \
--cc=sr@denx.de \
--cc=wd@denx.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