Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751981AbZJZNkW (ORCPT ); Mon, 26 Oct 2009 09:40:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751966AbZJZNkV (ORCPT ); Mon, 26 Oct 2009 09:40:21 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.124]:62287 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751601AbZJZNkT (ORCPT ); Mon, 26 Oct 2009 09:40:19 -0400 Subject: Re: Relicensing tracepoints and markers to Dual LGPL v2.1/GPL v2,headers to Dual BSD/GPL From: Steven Rostedt Reply-To: rostedt@goodmis.org To: Alan Cox Cc: Ingo Molnar , GeunSik Lim , Zhaolei , Wu Fengguang , Jesper Juhl , Mathieu Desnoyers , Adrian Bunk , Harvey Harrison , "Robert P. J. Day" , Jaswinder Singh Rajput , Frederic Weisbecker , Lai Jiangshan , KOSAKI Motohiro , linux-kernel@vger.kernel.org, Dominique Toupin , Michel Dagenais , Pierre-Marc Fournier In-Reply-To: <20091026101737.34697439@lxorguk.ukuu.org.uk> References: <20091023160257.GA30447@Krystal> <20091023160632.GA2198@Krystal> <20091026015357.GA6033@localhost> <023001ca55e1$436e38e0$808410ac@zhaoleiwin> <49b7c2350910252203o69811000w4551c01e6e2a10c7@mail.gmail.com> <20091026073048.GC8162@elte.hu> <20091026101737.34697439@lxorguk.ukuu.org.uk> Content-Type: text/plain Organization: Kihon Technologies Inc. Date: Mon, 26 Oct 2009 09:40:22 -0400 Message-Id: <1256564422.26028.248.camel@gandalf.stny.rr.com> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2303 Lines: 50 On Mon, 2009-10-26 at 10:17 +0000, Alan Cox wrote: > > > Can we re-distribute with dual license (e.g: bsd/gplv2 or lgpl > > > 2.1/gplv2) about some source of linux kernel source? I think that > > > linux kernel source is GPLv2 only. Frankly speaking, I am not know > > > exactly about legal issues of your questions. > > > > Yes, the legality of such relicensing is questionable as that code was > > never developed outside of the kernel but as part of the kernel. > > We have lots of dual licensed code in the kernel. The copy in kernel may > well only act as GPLv2 but the copy outside has other licences (Linus for > example relicensed some of his early locking primitive/atomic bits for > the Mozilla folks) > >From what I know (IANAL disclaimer) is that the Author of the code has the sole right (or employer of said Author) to decide what the license is. Not what project the code is used in. Unless there's some contract signed (like for most GNU projects). If you wrote the code, you have the right (or your employer) to pick and choose what license it is. You can change the license later on, but of course the code that went out under one license will stay under that license. But new releases can have the license change if all authors agree. > > So for those two grounds i cannot give my permission for this > > relicensing, sorry. > > One comment here - and one to be careful of for relicensing purposes. In > most parts of the world if you were paid by an employer to produce the > code that the request relates to then the rights to it belong solely to > the employer. Permission (or refusal) from the code author may well be > meaningless because such permission must come from the employer and right > owner in question (so IBM, Red Hat etc) in those cases and not the author. Correct, and that is why I went to Red Hat legal for this decision and I did not make it myself. I also (previously) listed the Red Hat employees that this decision covers. Red Hat has already given permission for the GPLv2/LGPL change. -- Steve -- 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/