From: Jesse Pollard <jesse@cats-chateau.net>
To: mru@kth.se (=?CP 1252?q?M=E5ns?= =?CP 1252?q?Rullg=E5rd?=)
Cc: linux-kernel@vger.kernel.org
Subject: Re: GPLv2 or not GPLv2? (no license bashing)
Date: Tue, 9 Mar 2004 11:38:56 -0600 [thread overview]
Message-ID: <04030911385603.32521@tabby> (raw)
In-Reply-To: <yw1xd67mhqyt.fsf@kth.se>
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.
prev parent reply other threads:[~2004-03-09 17:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 7:38 GPLv2 or not GPLv2? (no license bashing) Rolf Eike Beer
2004-03-04 7:44 ` [PATCH] Change "GPL" to "GPL v2" where files are GPLv2 Rolf Eike Beer
2004-03-04 7:44 ` [PATCH] Add missing "GPL" Rolf Eike Beer
2004-03-04 14:11 ` GPLv2 or not GPLv2? (no license bashing) Richard B. Johnson
2004-03-09 7:16 ` vda
2004-03-09 9:04 ` Måns Rullgård
2004-03-09 9:53 ` vda
2004-03-09 10:12 ` Måns Rullgård
2004-03-09 16:58 ` Jesse Pollard
2004-03-09 17:26 ` Måns Rullgård
2004-03-09 17:38 ` Jesse Pollard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=04030911385603.32521@tabby \
--to=jesse@cats-chateau.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@kth.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.