From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Ingo Brueckl <ib@wupperonline.de>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] unnecessary SCSI module
Date: Tue, 10 Mar 2009 09:46:30 -0500 [thread overview]
Message-ID: <1236696391.3316.6.camel@localhost.localdomain> (raw)
In-Reply-To: <49b60f4c@wupperonline.de>
On Tue, 2009-03-10 at 08:00 +0100, Ingo Brueckl wrote:
> James Bottomley <James.Bottomley@HansenPartnership.com> writes:
>
> >> When configuring MODULES with the kernel to be able to load external
> >> drivers coming as modules, but not using anything as module in the kernel
> >> itself, one would expect to end up in a module-free kernel. Currently, you
> >> don't if you use SCSI. You'll get one unnecessary module.
>
> > This isn't right because SCSI_SCAN_ASYNC only sets the *default*
> > behaviour of the kernel. Even if it's n the user can still boot up with
> > async scans by setting the kernel parameter.
>
> Ok, understood. But has it to be a module then? Why not giving the choice
> between building it directly into the kernel or as a module?
If you read through the threads, that question is answered.
> > It also keeps coming up regularly:
>
> Well, then something doesn't seem to be ok, does it? ;-)
James
next prev parent reply other threads:[~2009-03-10 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 19:06 [PATCH] unnecessary SCSI module Ingo Brueckl
2009-03-09 21:10 ` James Bottomley
2009-03-10 7:00 ` Ingo Brueckl
2009-03-10 14:46 ` James Bottomley [this message]
2009-03-10 17:24 ` Stefan Richter
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=1236696391.3316.6.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=ib@wupperonline.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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