From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: tigran@aivazian.fsnet.co.uk (Tigran Aivazian)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
andrea@suse.de (Andrea Arcangeli),
arjanv@redhat.com (Arjan van de Ven),
hugh@veritas.com (Hugh Dickins), mingo@redhat.com (Ingo Molnar),
stelian.pop@fr.alcove.com (Stelian Pop),
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.5.5] do export vmalloc_to_page to modules...
Date: Wed, 3 Apr 2002 22:48:20 +0100 (BST) [thread overview]
Message-ID: <E16ssc8-0004b2-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.33.0204032207170.1612-100000@einstein.homenet> from "Tigran Aivazian" at Apr 03, 2002 10:26:34 PM
> commercial vendors can take advantage of and we should be careful about it
> but I still believe that exporting or not exporting symbols based on
> _license_ is fundamentally wrong.
_INTERNAL is basically the same thing in effect anyway. It clearly states
the symbol is an internal part of a GPL product so it would be very hard
for someone to argue their work was not derivative if they used one
> (and really needed) a simple boundary provided by EXPORT_SYMBOL and
> EXPORT_SYMBOL_INTERNAL (if _GPL gets renamed to it) is, imho, sufficient.
BTW thinking about compatibility. There is no reason the view insmod sees
can't remain the same. EXPORT_SYMBOL_INTERNAL can just do the same symbol
magic as before.
It also helps me with the kernel-doc stuff if EXPORT_SYMBOL_INTERNAL is
used and in 2.5 we go mark most of the random internal kernel symbols with it
because we can begin to generate complete docs of public export interfaces
and their functionality
next prev parent reply other threads:[~2002-04-03 21:32 UTC|newest]
Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 13:13 Stelian Pop
2002-02-20 16:00 ` Hugh Dickins
2002-02-20 16:01 ` Arjan van de Ven
2002-04-03 16:21 ` Andrea Arcangeli
2002-04-03 17:43 ` Alan Cox
2002-04-03 18:13 ` Andrea Arcangeli
2002-04-03 19:11 ` Alan Cox
2002-04-03 19:23 ` Andrea Arcangeli
2002-04-03 20:05 ` Tigran Aivazian
2002-04-03 20:27 ` Tigran Aivazian
2002-04-03 21:22 ` Alan Cox
2002-04-03 21:26 ` Tigran Aivazian
2002-04-03 21:48 ` Alan Cox [this message]
2002-04-03 19:03 ` Tigran Aivazian
2002-04-03 19:10 ` Linus Torvalds
2002-04-03 19:19 ` Tigran Aivazian
2002-04-03 19:24 ` Linus Torvalds
2002-04-03 21:05 ` Tigran Aivazian
2002-04-03 21:25 ` Alan Cox
2002-04-04 6:43 ` Keith Owens
2002-04-04 10:22 ` Tigran Aivazian
2002-04-04 10:35 ` Arjan van de Ven
2002-04-04 11:54 ` Alan Cox
2002-04-04 12:01 ` Tigran Aivazian
2002-04-04 12:31 ` Adrian Bunk
2002-04-04 12:48 ` Russell King
2002-04-04 12:40 ` Russell King
2002-04-04 12:46 ` Tigran Aivazian
2002-04-05 7:29 ` David Schwartz
2002-04-05 8:24 ` Adrian Bunk
2002-04-05 8:28 ` David Schwartz
2002-04-04 13:26 ` Ingo Molnar
2002-04-04 15:21 ` Rik van Riel
2002-04-05 9:25 ` Paul Gortmaker
2002-04-04 15:35 ` Tigran Aivazian
2002-04-04 16:55 ` Andrea Arcangeli
2002-04-04 17:16 ` Christoph Hellwig
2002-04-04 17:46 ` Ingo Molnar
2002-04-04 17:59 ` Arjan van de Ven
2002-04-04 18:15 ` Rik van Riel
2002-04-05 0:47 ` Linux kernel and binary drivers (was: [PATCH 2.5.5] do export vmalloc_to_page to modules...) Steffen Persvold
2002-04-04 15:55 ` [PATCH 2.5.5] do export vmalloc_to_page to modules Richard B. Johnson
2002-04-04 16:14 ` Alan Cox
2002-04-04 16:15 ` Peter Horton
2002-04-04 16:23 ` Ingo Molnar
2002-04-04 16:38 ` Michael Clark
2002-04-04 20:57 ` Adrian Bunk
2002-04-04 16:44 ` Andrea Arcangeli
2002-04-04 17:16 ` Ingo Molnar
2002-04-04 18:00 ` Alan Cox
2002-04-04 16:42 ` Alexander Viro
2002-04-03 19:29 ` Andrea Arcangeli
2002-04-03 19:38 ` Alan Cox
2002-04-03 19:25 ` Linus Torvalds
2002-04-03 19:44 ` Alan Cox
2002-04-03 19:39 ` Linus Torvalds
2002-04-03 20:35 ` Gerd Knorr
2002-04-03 22:17 ` Richard B. Johnson
2002-04-03 22:24 ` Rik van Riel
2002-04-03 22:33 ` Tigran Aivazian
2002-04-03 22:35 ` David S. Miller
2002-04-06 9:08 ` David Woodhouse
2002-04-03 22:39 ` Rik van Riel
2002-04-04 5:59 ` Chris Wedgwood
2002-04-04 12:06 ` Alan Cox
2002-04-04 9:33 ` Ingo Molnar
2002-04-03 19:26 ` Andrea Arcangeli
2002-04-03 19:35 ` Alan Cox
2002-04-05 6:06 ` David Schwartz
2002-04-05 12:48 ` Alan Cox
2002-04-05 18:46 ` David Schwartz
2002-04-05 19:27 ` Alan Cox
2002-04-05 20:05 ` David Schwartz
2002-04-06 17:55 ` Alan Cox
2002-04-03 19:19 ` Alexander Viro
2002-04-03 21:07 ` David Schwartz
2002-04-03 21:33 ` Alan Cox
2002-04-03 21:28 ` Daniel Jacobowitz
2002-04-03 22:09 ` David Schwartz
2002-04-04 6:26 ` Kai Henningsen
2002-04-04 8:44 ` Adrian Bunk
2002-04-04 12:01 ` Alan Cox
2002-02-20 16:27 ` Ingo Molnar
2002-04-03 23:47 Petr Vandrovec
2002-04-04 0:19 ` Rik van Riel
2002-04-04 11:54 Petr Vandrovec
[not found] <Pine.LNX.4.44L.0204041217290.18660-100000@imladris.surriel .com>
2002-04-04 16:11 ` Anton Altaparmakov
2002-04-04 16:29 ` Ingo Molnar
[not found] <Pine.LNX.4.44.0204041123410.6422-100000@devserv.devel.redh at.com>
2002-04-04 17:06 ` Anton Altaparmakov
2002-04-04 17:55 ` Alan Cox
2002-04-04 17:52 ` Anton Altaparmakov
2002-04-04 17:27 Nicholas Berry
2002-04-05 13:22 Gareth Hughes
2002-04-09 6:55 Rick A. Hohensee
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=E16ssc8-0004b2-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=andrea@suse.de \
--cc=arjanv@redhat.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=stelian.pop@fr.alcove.com \
--cc=tigran@aivazian.fsnet.co.uk \
/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®