From: Rusty Russell <rusty@rustcorp.com.au>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Initcall depends
Date: Tue, 18 Jun 2002 07:43:02 +1000 [thread overview]
Message-ID: <20020618074302.1bc72b56.rusty@rustcorp.com.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0206162007160.30474-100000@chaos.physics.uiowa.edu>
On Sun, 16 Jun 2002 20:17:44 -0500 (CDT)
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de> wrote:
> As you're taking the effort of running some code to figure out the right
> ordering anyway, have you considered using the the information which is
> already there today, for all code which can be compiled modular.
Unfortunately, this is rather painful:
1) File A contains an initcall.
2) Find Module A which File A is part of.
3) For each exported symbol used by Module A
4) Find Module B which exports this symbol.
5) Find Files B which make up Module B.
6) For each initcall in Files B, insert a dependency.
Any clues for (2) and (5)?
Rusty.
--
there are those who do and those who hang on and you don't see too
many doers quoting their contemporaries. -- Larry McVoy
next prev parent reply other threads:[~2002-06-17 21:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-17 0:28 [PATCH] Initcall depends Rusty Russell
2002-06-17 1:17 ` Kai Germaschewski
2002-06-17 21:43 ` Rusty Russell [this message]
2002-06-17 22:43 ` Kai Germaschewski
2002-06-18 0:17 ` Rusty Russell
2002-06-18 10:55 ` Ingo Oeser
-- strict thread matches above, loose matches on Subject: below --
2002-07-22 8:46 Rusty Russell
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=20020618074302.1bc72b56.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.