From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755996Ab2DHUXP (ORCPT ); Sun, 8 Apr 2012 16:23:15 -0400 Received: from li9-11.members.linode.com ([67.18.176.11]:60229 "EHLO test.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753290Ab2DHUXO (ORCPT ); Sun, 8 Apr 2012 16:23:14 -0400 Date: Sun, 8 Apr 2012 16:23:10 -0400 From: "Ted Ts'o" To: "Luis R. Rodriguez" Cc: Linus Torvalds , rusty@rustcorp.com.au, linux-kernel@vger.kernel.org, Keith Packard , Ralf Baechle , David Woodhouse , Stephen Hemminger , "John W. Linville" , Greg Kroah-Hartman Subject: Re: [PATCH] module: Clarify GPL-Compatible is OK Message-ID: <20120408202310.GA17765@thunk.org> Mail-Followup-To: Ted Ts'o , "Luis R. Rodriguez" , Linus Torvalds , rusty@rustcorp.com.au, linux-kernel@vger.kernel.org, Keith Packard , Ralf Baechle , David Woodhouse , Stephen Hemminger , "John W. Linville" , Greg Kroah-Hartman References: <1333757482-16204-1-git-send-email-mcgrof@frijolero.org> <20120407024941.GB11295@thunk.org> <20120407211512.GC11295@thunk.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: tytso@thunk.org X-SA-Exim-Scanned: No (on test.thunk.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Apr 07, 2012 at 05:52:53PM -0700, Luis R. Rodriguez wrote: > > If you are really worried about people being upset that currently, you > > have to explicitly add a GPL license to BSD-licensed driver code > > before it gets imported into the kernel, and you are trying to > > sidestep the issue by adding a "GPL-Compatible" license (on the > > grounds that a BSD-only license qualifies as GPl-Compatible), let's > > have that debate openly, instead of trying to side-step it by adding > > "GPL-compatible" to include/linux/license.h and allowing BSD-only > > modules to use GPL-only symbols via a back door. > > I think you are implying that I want BSD licensed modules to use > GPL-only symbols. That is not the case. There are two things to > consider here and I think its best to separate them -- runtime and > stand alone file licenses. No, I wasn't thinking that; this is why I was asking what your motives were. I had *assumed* there were BSD'ites which were squicked out by even having the three letters "GPL" in the file in any shape or form, and so they wanted to keep a file licensed solely under a BSD-only (w/o the advertising clause), even if the driver was primarily being updated and maintained within the Linux kernel sources. I didn't pick up from your other e-mail that you were just going to use a MODULE_LICENSE of "GPL" which is just as good assuming the folks from BSD who wanted to share drivers were OK with it. - Ted