Content-Type: text/plain;
  charset="CP 1252"
From: Jesse Pollard <jesse@cats-chateau.net>
To: mru@kth.se (=?CP 1252?q?M=E5ns?= =?CP 1252?q?Rullg=E5rd?=)
Subject: Re: GPLv2 or not GPLv2? (no license bashing)
Date: Tue, 9 Mar 2004 11:38:56 -0600
Cc: linux-kernel@vger.kernel.org
References: <200403040838.31412.eike-kernel@sf-tec.de> <04030910585602.32521@tabby> <yw1xd67mhqyt.fsf@kth.se>
In-Reply-To: <yw1xd67mhqyt.fsf@kth.se>
MIME-Version: 1.0
Message-Id: <04030911385603.32521@tabby>
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1185
Lines: 25

On Tuesday 09 March 2004 11:26, M?ns Rullg?rd wrote:
> Jesse Pollard <jesse@cats-chateau.net> writes:
> > On Tuesday 09 March 2004 03:04, M?ns Rullg?rd wrote:
> >> vda <vda@port.imtp.ilyichevsk.odessa.ua> writes:
> >> > Well, Linux kernel is GPLed. If one adds his/hers code to the kernel
> >> > (s)he is automatically agrees to the terms of GPL.
> >> >
> >> > Because "adds code" is actually incorrect here.  "modifies existing
> >> > GPLed code" is more accurate.
> >>
> >> Suppose I write a new kernel module, without touching any existing
> >> code, and this module gets included in the kernel tree.  Have I added
> >> code?  Yes.  Have I modified GPLed code?  I think not.
> >
> > But you did incorporate GPL interfaces, likely some inline functions...
>
> Suppose for the sake of argument that I didn't.  Besides, simply
> including header files doesn't count.

Then your binary module is good to go... until the next patch or update.
-
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/