Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756242AbbBEEVT (ORCPT ); Wed, 4 Feb 2015 23:21:19 -0500 Received: from imap.thunk.org ([74.207.234.97]:54505 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751850AbbBEEVR (ORCPT ); Wed, 4 Feb 2015 23:21:17 -0500 Date: Wed, 4 Feb 2015 23:21:06 -0500 From: "Theodore Ts'o" To: Stefan Roese Cc: Greg Kroah-Hartman , monstr@monstr.eu, balbi@ti.com, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, Wolfgang Denk Subject: Re: SPDX-License-Identifier Message-ID: <20150205042106.GK2509@thunk.org> Mail-Followup-To: Theodore Ts'o , Stefan Roese , Greg Kroah-Hartman , monstr@monstr.eu, balbi@ti.com, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, Wolfgang Denk References: <774153d4-d33f-4bb4-813b-582762bc3af9@TX2EHSMHS021.ehs.local> <20140220182257.GF23217@saruman.home> <5306F458.9010706@monstr.eu> <20140221160442.GA17506@kroah.com> <5307790A.4050806@monstr.eu> <20140221161246.GM31902@saruman.home> <53077C5F.9000407@monstr.eu> <54CF9B12.2070807@denx.de> <20150202160622.GA9852@kroah.com> <54D24BA4.3070509@denx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54D24BA4.3070509@denx.de> User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: tytso@thunk.org X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1710 Lines: 39 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/