All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Warne <nick@ukfsn.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-scsi@vger.kernel.org
Subject: Re: scsi_wait_scan Kconfig option
Date: Fri, 7 Dec 2007 21:31:09 +0000	[thread overview]
Message-ID: <20071207213109.5a7a23fc@linuxamd.linicks.net> (raw)
In-Reply-To: <20071207194756.GB28914@parisc-linux.org>

Hi Matthew,

On Fri, 7 Dec 2007 12:47:56 -0700
Matthew Wilcox <matthew@wil.cx> wrote:

> On Fri, Dec 07, 2007 at 07:39:53PM +0000, Nick Warne wrote:
> > I try not to build a modular kernel, but only have modules ON due to
> > nVidia (sigh).  So I was semi-surprised when I saw the
> > scsi_wait_scan module being built again, yet NO WHERE in menuconfig
> > is it present to turn OFF.  Even if I hand edit .config, make puts
> > it back again...
> 
> You have modules on ... which means you might decide to load a scsi
> driver as a module.  Maybe one that isn't part of the source tree.
> The scsi_wait_scan module is only 1500 bytes.  Apart from a sense of
> ideological purity (odd in someone who chooses to use nVidia rather
> than, say, nv or nouveau), this really isn't a problem.

Alas the card I have isn't supported, but that debate isn't for here.

OK, I only have SCSI set for USB storage etc.  I find it strange that
this one and only option in the whole of Kconfig builds a module, and
yet, even though I know I will never need it, I can't stop it.

Surely if people build their own kernels, they should know (and) be
allowed to configure such options?

Nick 
-- 
Free Software Foundation Associate Member 5508

  reply	other threads:[~2007-12-07 21:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-07 19:39 Fw: scsi_wait_scan Kconfig option Nick Warne
2007-12-07 19:47 ` Matthew Wilcox
2007-12-07 21:31   ` Nick Warne [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-12-07 19:12 Nick Warne
2007-12-08 13:11 ` Clemens Koller
2007-12-08 16:21   ` Nick Warne
2007-12-08 21:21     ` Stefan Richter
2007-12-08 22:16       ` Matthew Wilcox

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=20071207213109.5a7a23fc@linuxamd.linicks.net \
    --to=nick@ukfsn.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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.