From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Roman Zippel <zippel@linux-m68k.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
torvalds@transmeta.com
Subject: Re: [PATCH] automatic initcalls
Date: Sat, 27 Jul 2002 23:51:32 -0400 [thread overview]
Message-ID: <3D436A44.8080505@mandrakesoft.com> (raw)
In-Reply-To: 20020728033359.7B2A2444C@lists.samba.org
Rusty Russell wrote:
> The more I play with these magic approaches, the more I prefer an
> explicit "Must be done after this" and "must be done before this":
> otherwise we're going to need to keep adding new levels as we discover
> something that doesn't fit in the magic 7.
I've always preferred a system where one simply lists dependencies [as
you describe above], and some program actually does the hard work of
chasing down all the initcall dependency checking and ordering.
Linus has traditionally poo-pooed this so I haven't put any work towards
it... but I still think it's a good idea, and something we will
eventually need as our system grows more complex. If someone stood up
and did the work, it should be pretty easy to generate a human-readable
list of dependencies so we can check the ordering and make sure it's
getting things right.
I wonder if there is some nifty ld feature I'm missing, that could do
this for us...
Jeff
next prev parent reply other threads:[~2002-07-28 3:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-27 20:22 [PATCH] automatic initcalls Roman Zippel
2002-07-28 3:31 ` Rusty Russell
2002-07-28 3:51 ` Jeff Garzik [this message]
2002-07-28 4:47 ` Linus Torvalds
2002-07-28 8:50 ` Keith Adamson
2002-07-28 18:59 ` Oliver Xymoron
2002-07-29 23:39 ` Rusty Russell
2002-07-29 8:39 ` Ingo Oeser
2002-07-30 2:49 ` Keith Adamson
2002-07-30 2:51 ` Keith Adamson
2002-07-28 12:18 ` Roman Zippel
2002-07-29 23:46 ` Rusty Russell
2002-07-30 23:04 ` [PATCH] automatic module_init ordering Roman Zippel
2002-07-31 2:33 ` Kai Germaschewski
2002-07-31 3:26 ` Rusty Russell
2002-07-31 17:06 ` Kai Germaschewski
2002-07-31 23:28 ` Rusty Russell
2002-07-28 21:59 ` [PATCH] automatic initcalls Kai Germaschewski
2002-07-29 18:56 ` Patrick Mochel
2002-07-29 20:14 ` Roman Zippel
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=3D436A44.8080505@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.com \
--cc=zippel@linux-m68k.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 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.