From: John Levon <moz@compsoc.man.ac.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: GPLONLY kernel symbols???
Date: Tue, 16 Oct 2001 18:07:57 +0100 [thread overview]
Message-ID: <20011016180757.A78456@compsoc.man.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.33.0110160927030.24895-100000@devel.office>
In-Reply-To: <Pine.LNX.4.33.0110160927030.24895-100000@devel.office>
On Tue, Oct 16, 2001 at 09:27:55AM -0700, Christoph Lameter wrote:
> /lib/modules/2.4.11/kernel/drivers/block/loop.o: Note: modules without a
> GPL compatible license cannot use GPLONLY_ symbols
>
> What is THAT?
A symbol that may only be referenced by GPL code.
The solution here is to add MODULE_LICENSE("GPL") into loop.c (probably)
or upgrade (assuming it's fixed later).
regards
john
p.s. upgrade anyway, 2.4.11 is a bad idea ...
--
"I hear you have four hundred and eighty six PCs for sale ?"
- Some Fool
next prev parent reply other threads:[~2001-10-16 17:07 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 16:27 GPLONLY kernel symbols??? Christoph Lameter
2001-10-16 17:07 ` John Levon [this message]
2001-10-16 17:22 ` Alexander Viro
2001-10-17 2:17 ` Keith Owens
2001-10-17 4:59 ` Christoph Lameter
2001-10-17 5:54 ` Keith Owens
2001-10-17 6:15 ` Christoph Lameter
2001-10-17 18:28 ` Gerhard Mack
2001-10-17 19:34 ` Ben Greear
2001-10-17 20:18 ` pierre
2001-10-17 19:34 ` Wayne Whitney
2001-10-17 21:31 ` pierre
2001-10-17 20:32 ` Arjan van de Ven
2001-10-17 19:14 ` David Lang
2001-10-17 20:37 ` Arjan van de Ven
2001-10-17 19:20 ` David Lang
2001-10-17 22:02 ` pierre
2001-10-18 13:45 ` M. R. Brown
2001-10-21 16:05 ` Alan Cox
2001-10-18 13:32 ` M. R. Brown
2001-10-17 14:15 ` John Levon
2001-11-13 2:57 ` Richard Gooch
2001-11-13 3:21 ` Dave Jones
2001-11-13 3:24 ` Richard Gooch
2001-11-13 3:53 ` Alexander Viro
2001-11-13 3:58 ` Richard Gooch
2001-11-13 4:10 ` Alexander Viro
2001-11-13 4:21 ` Richard Gooch
2001-11-13 4:36 ` Alexander Viro
2001-11-13 4:49 ` Richard Gooch
2001-11-13 10:46 ` Martin Dalecki
2001-11-13 4:15 ` Jeff Garzik
2001-11-13 4:37 ` Richard Gooch
2001-11-13 4:49 ` Alexander Viro
2001-11-13 5:03 ` Richard Gooch
2001-11-13 5:27 ` Alexander Viro
2001-11-13 5:35 ` Richard Gooch
2001-11-13 5:44 ` Jeff Garzik
2001-11-13 4:54 ` Jeff Garzik
2001-11-13 5:00 ` Richard Gooch
2001-11-13 5:14 ` Jeff Garzik
2001-11-13 5:23 ` Richard Gooch
2001-11-13 5:29 ` Robert Love
2001-11-13 5:44 ` Erik Andersen
2001-11-13 5:56 ` Richard Gooch
2001-11-13 4:58 ` Davide Libenzi
2001-11-13 5:07 ` John Alvord
2001-11-28 22:41 ` Dr. Kelsey Hudson
2001-11-29 0:35 ` Michael H. Warfield
2001-11-29 5:04 ` Dr. Kelsey Hudson
2001-11-13 10:01 ` Alan Cox
2001-11-13 10:29 ` Jeff Garzik
2001-11-13 13:47 ` Dave Jones
2001-11-13 16:54 ` Alan Cox
2001-11-13 17:17 ` Dave Jones
2001-11-15 10:03 ` [PATCH] mtrr (was Re: GPLONLY kernel symbols???) Paul Gortmaker
2001-11-13 10:48 ` GPLONLY kernel symbols??? Martin Dalecki
2001-11-13 9:57 ` [OT] Coding Style (was: Re: GPLONLY kernel symbols???) Henning P. Schmiedehausen
2001-11-28 22:35 ` GPLONLY kernel symbols??? Dr. Kelsey Hudson
2001-11-13 9:52 ` Roman Zippel
2001-11-13 4:05 ` Jeff Garzik
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=20011016180757.A78456@compsoc.man.ac.uk \
--to=moz@compsoc.man.ac.uk \
--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