From: Seongsu Lee <senux@senux.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: specifying the order of calling kernel functions (or modules)
Date: Tue, 10 Oct 2006 23:09:33 +0900 [thread overview]
Message-ID: <20061010140933.GA16075@pooky.senux.com> (raw)
In-Reply-To: <20061007082752.6ff90517.rdunlap@xenotime.net>
On Sat, Oct 07, 2006 at 08:27:52AM -0700, Randy Dunlap wrote:
> On Sat, 7 Oct 2006 23:41:39 +0900 Seongsu Lee wrote:
>
> > Hello,
> >
> > Thank you for the replys.
> >
> > I try to phrase differently.
> >
> > I made a simple kernel module that do 'hello world'. The module will be
> > called when I do 'modprobe' or 'insmod' to load it into the memory.
> >
> > When is the function, init_module(), in the module called in the case
> > the module is compiled as a built-in one? (Not M but Y in .config)
> > Can I specify the exact time of calling the function, init_module() in
> > the module?
>
> That depends on the order that it is listed in the (nested)
> Makefiles. Which sub-directory and Makefile will you use?
drivers/mtd/Makefile
Yes, I confirmed that the order of being called is same with
the order that is listed in the Makefiles.
I think it is better to post questions of kernel newbie like this
into other mailing lists instead of this, developer list.
Anyway, thank you very much for your help.
--
Seongsu Lee - http://www.senux.com/
Your job is being a professor and researcher: That's
one hell of a good excuse for some of the
brain-damages of minix. (Linus Torvalds to Andrew
Tanenbaum)
prev parent reply other threads:[~2006-10-10 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 10:17 specifying the order of calling kernel functions (or modules) Seongsu Lee
2006-09-28 15:47 ` Valdis.Kletnieks
2006-09-30 10:42 ` Seongsu Lee
2006-09-30 16:47 ` Randy Dunlap
2006-10-07 14:41 ` Seongsu Lee
2006-10-07 15:27 ` Randy Dunlap
2006-10-10 14:09 ` Seongsu Lee [this message]
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=20061010140933.GA16075@pooky.senux.com \
--to=senux@senux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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