From: Dan Aloni <da-x@gmx.net>
To: jt@hpl.hp.com
Cc: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jeff Garzik <jgarzik@mandrakesoft.com>
Subject: Re: Link order madness :-(
Date: Mon, 3 Jun 2002 20:47:02 +0300 [thread overview]
Message-ID: <20020603174702.GA1488@callisto.yi.org> (raw)
In-Reply-To: <20020601065520.GA11951@callisto.yi.org> <Pine.LNX.4.44.0206010235340.21152-100000@chaos.physics.uiowa.edu> <20020603101447.A6067@bougret.hpl.hp.com>
On Mon, Jun 03, 2002 at 10:14:47AM -0700, Jean Tourrilhes wrote:
> On Sat, Jun 01, 2002 at 02:43:14AM -0500, Kai Germaschewski wrote:
> > On Sat, 1 Jun 2002, Dan Aloni wrote:
> >
> > > > So, I was trying to fix that, and I found a problem with
> > > > kernel link order.
> > >
> > > It is possible that recent kbuild changes caused that.
> >
> > I don't think so, I took extra care to leave it all the same. (Well,
> > except for sound/, which is outside drivers/) It'd however surely be a
> > good idea to go through it and document which dependencies there are.
>
> Obviously Dan didn't bother to read my e-mail. The problem is
> definitely not with kbuild. The problem is with the
> __define_initcall() levels.
I did in fact read your e-mail. I was just suggesting something that is
drawn from previous experience concerning dependency problems with drivers
compiled in as non-modules. And in my e-mail I was suggesting a workaround
to make sure stuff gets initialized regardless of __initcall() levels.
--
Dan Aloni
da-x@gmx.net
prev parent reply other threads:[~2002-06-03 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-01 0:21 Jean Tourrilhes
2002-06-01 6:55 ` Dan Aloni
2002-06-01 7:43 ` Kai Germaschewski
2002-06-03 17:14 ` Jean Tourrilhes
2002-06-03 17:29 ` Horst von Brand
2002-06-03 17:52 ` Nathan
2002-06-03 18:13 ` Thunder from the hill
2002-06-03 17:47 ` Dan Aloni [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=20020603174702.GA1488@callisto.yi.org \
--to=da-x@gmx.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@mandrakesoft.com \
--cc=jt@hpl.hp.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®