From: Alan Cox <alan@redhat.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: davids@webmaster.com, Valdis.Kletnieks@vt.edu,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
linux-kernel@vger.kernel.org, Alan Cox <alan@redhat.com>
Subject: Re: [PATCH] 2.6.25-rc2-mm1 - fix mcount GPL bogosity.
Date: Tue, 26 Feb 2008 12:21:43 -0500 [thread overview]
Message-ID: <20080226172143.GA5445@devserv.devel.redhat.com> (raw)
In-Reply-To: <m34pbv8x8s.fsf@maximus.localdomain>
On Tue, Feb 26, 2008 at 06:04:51PM +0100, Krzysztof Halasa wrote:
> 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. OTOH GPL symbols give
They can claim that anyway. The can claim to be alien life forms too. Claim
is not the same as legal decision. From what I've seen its helped make binary
module abusers more cautious.
Alan
next prev parent reply other threads:[~2008-02-26 17:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 17:59 [PATCH] 2.6.25-rc2-mm1 - fix mcount GPL bogosity 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 [this message]
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
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:
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=20080226172143.GA5445@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=acme@ghostprotocols.net \
--cc=akpm@linux-foundation.org \
--cc=davids@webmaster.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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