kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: dshwatrz@gmail.com (David Shwatrz)
To: kernelnewbies@lists.kernelnewbies.org
Subject: order of call to built-in modules
Date: Mon, 11 Apr 2011 23:04:55 +0300	[thread overview]
Message-ID: <BANLkTikCZAUzjempBfOk+UOeHOM1PXM53A@mail.gmail.com> (raw)

HI,
The macros module_init() and module_exit() are used both in case
a source is built-in (the code is called from the init stage) or as a
kernel module (implementing a init_module symbol).

In case 2 of /built-in/ modules  I am wondering if it is
possible to know by advance the order used to call the various
module_init() entry points. Is it possible to fix this order?
rgs,
DS

             reply	other threads:[~2011-04-11 20:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11 20:04 David Shwatrz [this message]
2011-04-11 20:16 ` order of call to built-in modules Greg KH
2011-04-11 20:19 ` Gasparini Andrea
2011-04-11 21:04 ` Manish Katiyar

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=BANLkTikCZAUzjempBfOk+UOeHOM1PXM53A@mail.gmail.com \
    --to=dshwatrz@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).