mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: djweis@sjdjweis.com (David Weis)
Cc: linux-kernel@vger.kernel.org
Subject: Re: GPL Question
Date: Fri, 27 Oct 2000 18:21:27 +0100 (BST)	[thread overview]
Message-ID: <E13pDC5-0004g7-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.10.10010271130550.23907-100000@catbert.desm.plconline.com> from "David Weis" at Oct 27, 2000 11:31:52 AM

> On Fri, 27 Oct 2000, Jason Wohlgemuth wrote:
> 
> > Now, if a module is loaded that registers a set of functions that have 
> > increased functionality compared to the original functions, if that 
> > modules is not based off GPL'd code, must the source code of that module 
> > be released under the GPL?
> 
> It would probably follow GPL, but it's pretty slimy. I won't buy it.

It depends primarily if the module depends on the code which is GPL. Its all
a rather unclear area. 

Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-10-27 17:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-27 16:36 Jason Wohlgemuth
2000-10-27 16:31 ` David Weis
2000-10-27 17:21   ` Alan Cox [this message]
2000-10-27 17:26     ` Matthew Dharm
2000-10-27 17:56       ` Somewhat different " Christopher Friesen
2000-10-27 18:06         ` Rik van Riel
2000-10-27 20:49           ` Alan Cox
2000-10-27 17:16 ` Mark Salisbury
2000-10-27 17:23 ` Alan Cox
2000-10-27 18:53 ` David Schwartz
2000-10-27 18:56   ` Rik van Riel
2000-10-27 20:53     ` Alan Cox
2000-10-27 19:17   ` James Sutherland
2000-10-27 21:08     ` Brian F. G. Bidulock
2000-10-27 20:52   ` Alan Cox
2000-10-30 12:27     ` Helge Hafting
2004-06-28 22:13 GPL question ca_tex-kernel
2004-06-29 11:01 ` David Weinehall

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=E13pDC5-0004g7-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=djweis@sjdjweis.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®