From: Rusty Russell <rusty@rustcorp.com.au>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>,
kai@germaschewski.name, Sam Ravnborg <sam@ravnborg.org>,
Vincent Vanackere <vincent.vanackere@gmail.com>,
keenanpepper@gmail.com,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Undefined symbols in 2.6.11-rc5-mm1
Date: Fri, 04 Mar 2005 21:23:17 +1100 [thread overview]
Message-ID: <1109931797.28203.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20050302140019.GC4608@stusta.de>
On Wed, 2005-03-02 at 15:00 +0100, Adrian Bunk wrote:
> Why doesn't an EXPORT_SYMBOL create a reference?
It does: EXPORT_SYMBOL(x) drops the address of "x", including
__attribute_used__, in the __ksymtab section.
However, if CONFIG_MODULES=n, it does nothing: perhaps that is what you
are seeing.
Rusty.
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
next prev parent reply other threads:[~2005-03-04 17:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 5:37 Undefined symbols in 2.6.11-rc5-mm1 Keenan Pepper
2005-03-02 9:23 ` Andrew Morton
2005-03-02 9:45 ` Vincent Vanackere
2005-03-02 11:24 ` Andrew Morton
2005-03-02 13:26 ` Vincent Vanackere
2005-03-02 14:00 ` Adrian Bunk
2005-03-02 16:28 ` Andrew Morton
2005-03-02 17:23 ` Valdis.Kletnieks
2005-03-02 17:34 ` Andrew Morton
2005-03-04 10:26 ` Rusty Russell
2005-03-03 13:41 ` Adrian Bunk
2005-03-04 10:23 ` Rusty Russell [this message]
2005-03-04 18:56 ` Adrian Bunk
2005-03-04 19:13 ` Adrian Bunk
2005-03-04 19:11 ` Kai Germaschewski
2005-03-04 20:28 ` Adrian Bunk
2005-03-05 5:09 ` Kai Germaschewski
2005-03-05 13:04 ` Adrian Bunk
2005-03-05 15:19 ` Kai Germaschewski
2005-03-05 15:36 ` Adrian Bunk
2005-03-05 16:36 ` Kai Germaschewski
2005-03-05 17:15 ` Adrian Bunk
2005-03-05 18:48 ` Kai Germaschewski
2005-03-05 23:58 ` Christoph Hellwig
2005-03-05 23:57 ` Christoph Hellwig
[not found] ` <4225C613.7010701@gmail.com>
2005-03-02 14:03 ` Keenan Pepper
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=1109931797.28203.2.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=kai@germaschewski.name \
--cc=keenanpepper@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=vincent.vanackere@gmail.com \
/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