LKML Archive on
help / color / mirror / Atom feed
From: Krzysztof Halasa <>
Cc: <>,
	"Andrew Morton" <>,
	"Ingo Molnar" <>,
	"Arnaldo Carvalho de Melo" <>,
	<>, "Alan Cox" <>
Subject: Re: [PATCH] 2.6.25-rc2-mm1 - fix mcount GPL bogosity.
Date: Wed, 27 Feb 2008 00:13:31 +0100	[thread overview]
Message-ID: <m3ir0bcnvo.fsf@maximus.localdomain> (raw)
In-Reply-To: <> (David Schwartz's message of "Tue\, 26 Feb 2008 10\:19\:42 -0800")

"David Schwartz" <> writes:

> The agreement made when the feature was added was that EXPORT_GPL was not a
> license enforcement mechanism but was an indication that someone believed
> that any use of the symbol was possible only a derivative work that would
> need to be distributed under the GPL.

But the above gives us nothing.
*If* any use of non-GPL symbols only by a binary module was ok then it
would make sense.

>> Actually I think the _GPL exports are really harmful - somebody
>> distributing a binary module may claim he/she doesn't violate the GPL
>> because the module uses only non-GPL exports.
> Anyone can argue anything. That would be an obviously stupid argument.
> Perhaps clearer documentation might be helpful, but the GPL speaks for
> itself.

Not sure if the court would share this opinion.
Defendant: my module doesn't use any GPL-only export!
Plaintiff: but using XXX normal symbol is a violation too!
D: so why have you created that _GPL thing exactly?

D: top of the COPYING file explicity states binary modules are ok.

This is of course fine if we consider normal use of non-GPL-only
symbols ok.

> They serve as a warning and, as a practical matter, may make it a bit more
> difficult to violate the license.

Technically only.

I have to agree with Alan that the list of non-GPL modules only is
quite tiny nowadays. Madwifi is in terminal state, ATI is opening the
docs and working on GPL driver, modem drivers are mostly thing of
the past, NVidias will probably be supported by the open source driver
soon even if they don't open their code.

Embedded devices have full Linux, not just modules.
Krzysztof Halasa

  reply	other threads:[~2008-02-26 23:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-25 17:59 Valdis.Kletnieks
2008-02-25 18:23 ` Steven Rostedt
2008-02-25 18:19   ` Alan Cox
2008-02-25 19:27     ` Adrian Bunk
2008-02-25 19:48       ` Alan Cox
2008-02-25 20:09         ` Adrian Bunk
2008-02-25 20:38           ` Alan Cox
2008-02-25 21:17       ` Valdis.Kletnieks
2008-02-26  1:30   ` David Schwartz
2008-02-26 12:29     ` Alan Cox
2008-02-26 15:43     ` Krzysztof Halasa
2008-02-26 17:04       ` Krzysztof Halasa
2008-02-26 17:21         ` Alan Cox
2008-02-26 17:44           ` Krzysztof Halasa
2008-02-26 18:04             ` Alan Cox
2008-02-26 18:19       ` David Schwartz
2008-02-26 23:13         ` Krzysztof Halasa [this message]
2008-02-26 23:35           ` David Schwartz
2008-02-27  0:05             ` Krzysztof Halasa
2008-02-27  0:28               ` David Schwartz
2008-02-27 10:31           ` Alan Cox
2008-02-27 10:55             ` Krzysztof Halasa

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3ir0bcnvo.fsf@maximus.localdomain \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH] 2.6.25-rc2-mm1 - fix mcount GPL bogosity.' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).