Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759817AbYAULbm (ORCPT ); Mon, 21 Jan 2008 06:31:42 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758700AbYAULbd (ORCPT ); Mon, 21 Jan 2008 06:31:33 -0500 Received: from fk-out-0910.google.com ([209.85.128.185]:65184 "EHLO fk-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758033AbYAULbc (ORCPT ); Mon, 21 Jan 2008 06:31:32 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:x-x-sender:to:cc:subject:in-reply-to:message-id:references:mime-version:content-type; b=QV0EEMa3xIOn471IjkL1DtvZsXVH/k4a2pdOE7puQhZ/WAP/stFJKz4sdxDdzAnPH5leb4qxv3w/EQC2E+VWb1JNWkWFbdWCH1zTqvF//K4Vfx5LN8zBbRG0hlBLDPzM48h+T1wBYg0KNLHXd1kPpts/MOUGnQDGzsjSdaFKJbA= Date: Mon, 21 Jan 2008 12:31:20 +0100 (CET) From: Esben Nielsen X-X-Sender: simlo@frodo.shire To: Steven Rostedt cc: Valdis.Kletnieks@vt.edu, caglar@pardus.org.tr, LKML , RT , Ingo Molnar , Thomas Gleixner , Alan Cox Subject: Re: 2.6.24-rc7-rt2 In-Reply-To: Message-ID: References: <1200336080.318.8.camel@localhost.localdomain> <200801150237.44029.caglar@pardus.org.tr> <24149.1200455417@turing-police.cc.vt.edu> <31516.1200464589@turing-police.cc.vt.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2506 Lines: 59 On Wed, 16 Jan 2008, Steven Rostedt wrote: > > On Wed, 16 Jan 2008, Steven Rostedt wrote: >> >> We modified mcount now, and it is derived from an objdump of glibc. So >> this is most definitely a "derived" work from glibc. But glibc is licensed >> as LGPL, which IIRC allows for non GPL to link to it. >> >> I personally could care less if we use EXPORT_SYMBOL or EXPORT_SYMBOL_GPL. >> But I really want to do The Right Thing(tm). I'm not a lawyer and don't >> claim that I know anything about the law, but I'm leaning towards the non >> _GPL version because the code was from LGPL and not from strict GPL. > > Sorry folks, I'm going to stick with the _GPL version. It doesn't mean > that you can't still load your nVidia module into -rt. I just means you > can't turn on function trace and then load it. Well, you might if you > don't compile the nVidia wrapper against it with function trace on. > > The reason simply is to cover my butt. By limiting it to GPL, I'm fine. > Even if the original author didn't care. But by opening it up to external > prorietary modules, I may be considered infringing on the license. > > So, unless I hear from a lawyer that is willing to back me up on a non > _GPL export publically, the mcount function will stay as an > EXPORT_SYMBOL_GPL. > > Note: There is a definite reason for this change. The previous version > of mcount was written by Ingo Molnar, and he added the export. I've > changed mcount to be closer to the glibc code (which I derived it from), > so the change in EXPORT type is legitimate. > > -- Steve Please, tell what in the license forbids me to make a global replacement EXPORT_SYMBOL_GPL -> EXPORT_SYMBOL and distribute the result? For me, on the other hand, it is against the spirit of free software to actively make a block for people to do what ever they want with the code when they are only doing it to themselves. That includes loading non-GPL software into the kernel. The only thing they are not allowed to do is to distribute it and in that way "hurt" other people. Esben > - > To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- 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/