From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Modutils 2.5 change, start running this command now
Date: Fri, 12 Oct 2001 08:34:23 +0200 [thread overview]
Message-ID: <20011012083423.M30515@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <25612.1002800758@ocs3.intra.ocs.com.au>
In-Reply-To: <25612.1002800758@ocs3.intra.ocs.com.au>; from kaos@ocs.com.au on Thu, Oct 11, 2001 at 09:45:58PM +1000
On Thu, Oct 11, 2001 at 09:45:58PM +1000, Keith Owens wrote:
> In current modutils, a module that does not export symbols and does not
> say EXPORT_NO_SYMBOLS will default to exporting all symbols. This is a
> hangover from kernel 2.0 and will be removed when modutils 2.5 appears,
> shortly after the kernel 2.5 branch is created.
Will it still be done, if we put it on the "export-objs" list?
Putting an explicit "EXPORT_SYMBOL(foo)" only encourages people
not to look what they can prepend with "static". Everything not
static is the C-definition of "exporting".
EXPORT_SYMBOL is nice, if you have modules consisting of multiple
objects, that need to share variables/functions but should not be
needed, if the module-author knows sth. about proper design.
Regards
Ingo Oeser
next prev parent reply other threads:[~2001-10-12 6:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 11:45 Keith Owens
2001-10-12 6:34 ` Ingo Oeser [this message]
2001-10-12 10:04 ` Benjamin LaHaise
2001-10-12 11:37 ` Keith Owens
2001-10-12 12:14 ` David Woodhouse
2001-10-12 14:40 ` Keith Owens
2001-10-12 15:01 ` Tom Rini
2001-10-15 16:05 ` [PATCH] meye camera driver EXPORT_NO_SYMBOLS Stelian Pop
-- strict thread matches above, loose matches on Subject: below --
2001-10-03 4:36 Modutils 2.5 change, start running this command now Keith Owens
2001-10-03 4:48 ` Robert Love
2001-10-03 8:17 ` Russell King
2001-10-03 11:59 ` Keith Owens
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=20011012083423.M30515@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=kaos@ocs.com.au \
--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
all inboxes | Powered by JetHome®