public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [BUG?] 2.5.71 removed request_module("scsi_hostadapter")
Date: Thu, 17 Jul 2003 11:31:58 +0100	[thread overview]
Message-ID: <20030717113158.B18620@infradead.org> (raw)
In-Reply-To: <200307161145.h6GBjaSi025681@harpo.it.uu.se>; from mikpe@csd.uu.se on Wed, Jul 16, 2003 at 01:45:36PM +0200

On Wed, Jul 16, 2003 at 01:45:36PM +0200, Mikael Pettersson wrote:
> While trying to figure out why my SCSI modules don't autoload
> properly in 2.6.0-test1 and late 2.5 kernels, I found that
> patch-2.5.71 removed scsi.c's request_module("scsi_hostadapter").
> It seems that some driver model conversion changed scsi_register_device()
> to scsi_register_{driver,interface}(), but the latter don't do
> anything wrt autoloading the host adapter.
> 
> Is this an oversight or is it intensional?

It's intentional.

> I can probably work around this through "install" command
> kludgery in /etc/modprobe.conf, but that's (a) is ugly, and
> (b) probably won't work for configs with built-in SCSI core
> but modular host adapter.

builtin scsi core doesn't matter for this at all, the question
is whether the highlevel drivers are compiled in or not.

modular highlevel driver(s)

	simples postinst in old-style modules.conf (or some rusty equivalent)

builtin highlevel driver(s)

	the request_module is useless anyway as it happens before root is
	mounted.

      reply	other threads:[~2003-07-17 10:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-16 11:45 [BUG?] 2.5.71 removed request_module("scsi_hostadapter") Mikael Pettersson
2003-07-17 10:31 ` Christoph Hellwig [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=20030717113158.B18620@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    /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