From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: trini@kernel.crashing.org (Tom Rini)
Cc: laughing@shared-source.org (Alan Cox), linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.9-ac16
Date: Fri, 28 Sep 2001 00:06:44 +0100 (BST) [thread overview]
Message-ID: <E15mkEu-0005QS-00@the-village.bc.nu> (raw)
In-Reply-To: <20010927120353.M13535@cpe-24-221-152-185.az.sprintbbd.net> from "Tom Rini" at Sep 27, 2001 12:03:53 PM
> > 2.4.9-ac16
> [snip]
> > o Add initial pieces for EXPORT_SYMBOL_GPL (me)
> > | kernel symbols for GPL only use
>
> What's the idea behind this? Are we now going to restrict certain parts of
> the kernel to interacting with GPL-only modules?
Imagine you have a shared library of code that makes writing some kind of
driver easier, and you don't see why it should be available to non GPL
driver modules.
Linus has made it absolutely (as in he'll send out the killer penguin with
chainsaw if need be) clear that existing symbols wont mysteriously turn GPL
only.
Alan
next prev parent reply other threads:[~2001-09-27 23:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-27 17:51 Linux 2.4.9-ac16 Alan Cox
2001-09-27 18:26 ` Udo A. Steinberg
2001-09-27 18:28 ` Rik van Riel
2001-09-27 19:03 ` [PATCH] 2.4.9-ac16 swapoff 2*vfree Hugh Dickins
2001-09-27 19:36 ` Alexander Viro
2001-09-27 19:03 ` Linux 2.4.9-ac16 Tom Rini
2001-09-27 23:06 ` Alan Cox [this message]
2001-09-27 23:11 ` Tom Rini
2001-09-27 19:31 ` Kent Borg
2001-09-28 1:07 ` [REPORT] (PPC) Compile Error (Linux 2.4.9-ac[12-16]) Tsunehiko Baba
2001-09-28 14:15 ` Tom Rini
2001-09-28 14:40 ` Alan Cox
2001-09-28 14:41 ` Tom Rini
2001-09-28 5:21 ` [PATCH] link failur in Linux 2.4.9-ac16 around apm.o and sysrq.o junio
2001-09-28 5:47 ` junio
2001-09-28 15:41 ` Randy.Dunlap
2001-09-28 15:58 ` Crutcher Dunnavant
2001-09-28 15:30 ` Linux 2.4.9-ac16 Stefan Becker
2001-09-28 16:39 ` Rik van Riel
2001-09-28 17:15 ` Tim Connors
2001-09-28 20:52 ` Russell King
2001-09-28 7:03 Pau Aliagas
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=E15mkEu-0005QS-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=laughing@shared-source.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).