From: Keith Owens <kaos@ocs.com.au>
To: "Antti Halonen" <antti.halonen@secgo.com>
Cc: "linux-os (Dick Johnson)" <linux-os@analogic.com>,
"Linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: searching exported symbols from modules
Date: Fri, 21 Apr 2006 17:33:07 +1000 [thread overview]
Message-ID: <14930.1145604787@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Wed, 19 Apr 2006 16:08:37 +0300." <963E9E15184E2648A8BBE83CF91F5FAF43619A@titanium.secgo.net>
"Antti Halonen" (on Wed, 19 Apr 2006 16:08:37 +0300) wrote:
>
>Hi Dick,
>
>Thanks for your response.
>
>> `insmod` (or modprobe) does all this automatically. Anything that's
>> 'extern' will get resolved. You don't do anything special. You can
>> also use `depmod` to verify that you won't have any problems loading.
>> `man depmod`.
>
>Yes, I know insmod and herein the problem lies. I have a module where
>I want to use functions provided by another module, _if_ it is present,
>otherwise use modules internal functions.
symbol_get() and symbol_put(). See include/linux/module.h. If
symbol_get() returns NULL then the symbol does not exist.
next prev parent reply other threads:[~2006-04-21 7:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 13:08 searching exported symbols from modules Antti Halonen
2006-04-19 14:55 ` linux-os (Dick Johnson)
2006-04-19 15:53 ` Robin Holt
2006-04-21 7:33 ` Keith Owens [this message]
2006-04-21 14:03 ` Vernon Mauery
-- strict thread matches above, loose matches on Subject: below --
2006-04-20 7:15 Antti Halonen
2006-04-20 8:01 ` Kyle Moffett
2006-04-20 17:00 ` Adrian Bunk
2006-04-20 6:12 Antti Halonen
2006-04-20 7:00 ` Kyle Moffett
2006-04-20 5:50 Antti Halonen
2006-04-20 5:59 ` James Morris
2006-04-19 15:59 Antti Halonen
2006-04-19 16:02 ` Arjan van de Ven
2006-04-19 15:34 Antti Halonen
2006-04-19 15:43 ` Arjan van de Ven
2006-04-19 14:54 Antti Halonen
2006-04-19 15:17 ` Arjan van de Ven
2006-04-19 12:44 Antti Halonen
2006-04-19 12:59 ` linux-os (Dick Johnson)
2006-04-19 14:55 ` Jim Cromie
2006-04-19 14:22 ` Arjan van de Ven
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=14930.1145604787@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=antti.halonen@secgo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.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