public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
Cc: Dan Aloni <karrde@callisto.yi.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Jens Axboe <axboe@image.dk>
Subject: Re: cdrom driver dependency problem (and a workaround patch)
Date: Sat, 21 Apr 2001 13:45:54 +0200	[thread overview]
Message-ID: <20010421134554.E26732@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.32.0104210107160.1148-100000@callisto.yi.org> <20010421134412.O682@nightmaster.csn.tu-chemnitz.de>
In-Reply-To: <20010421134412.O682@nightmaster.csn.tu-chemnitz.de>; from ingo.oeser@informatik.tu-chemnitz.de on Sat, Apr 21, 2001 at 01:44:12PM +0200

On Sat, Apr 21 2001, Ingo Oeser wrote:
> On Sat, Apr 21, 2001 at 02:17:18AM +0300, Dan Aloni wrote:
> > One reason for this misdependency is that the IDE is initialized before
> > the cdrom driver, register_cdrom() gets called from inside the IDE
> > initialization functions. (ide_init() -> ide_init_builtin_drivers() ->
> > ide_cdrom_init() -> ide_cdrom_setup() -> ide_cdrom_register() ->
> > register_cdrom())
> > 
> > In order to get my kernel to boot, I've made the following temporary
> > workaround patch. I'd be glad to hear about other ways of solving this.
> 
> The link order is wrong. So why not changing the link order then?

That's perfect, I just hadn't looked into that. The superior solution,
clearly, thanks!

-- 
Jens Axboe


  reply	other threads:[~2001-04-21 11:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-20 23:17 cdrom driver dependency problem (and a workaround patch) Dan Aloni
2001-04-21 11:44 ` Ingo Oeser
2001-04-21 11:45   ` Jens Axboe [this message]
2001-04-21 17:33   ` Dan Aloni
2001-04-21 19:26     ` Ingo Oeser
2001-04-21 19:55       ` Dan Aloni

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=20010421134554.E26732@suse.de \
    --to=axboe@suse.de \
    --cc=axboe@image.dk \
    --cc=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=karrde@callisto.yi.org \
    --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