From: Nick Warne <nick@ukfsn.org>
To: Clemens Koller <clemens.koller@anagramm.de>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: scsi_wait_scan Kconfig option
Date: Sat, 8 Dec 2007 16:21:22 +0000 [thread overview]
Message-ID: <20071208162122.7e77601e@linuxamd.linicks.net> (raw)
In-Reply-To: <475A9810.4070104@anagramm.de>
On Sat, 08 Dec 2007 14:11:44 +0100
Clemens Koller <clemens.koller@anagramm.de> wrote:
> Nick Warne schrieb:
> > I am bringing this up again - primarily as I forgot about it after
> > patching my build tree ages ago:
> >
> > http://lkml.org/lkml/2007/10/27/68
Subject: Re: Fw: scsi_wait_scan Kconfig option
Date: Fri, 7 Dec 2007 12:47:56 -0700
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...
On Fri, 7 Dec 2007 12:47:56 -0700
Matthew Wilcox <matthew@wil.cx> wrote:
> 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.
>
> Please see the patch I sent some days ago, which does the very
> same thing: http://marc.info/?l=linux-kernel&m=119677244318528&w=2
>
> True...
Well, that's two of us would that like to be able to stop it
building :-)
Nick
--
Free Software Foundation Associate Member 5508
next parent reply other threads:[~2007-12-08 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071207191242.71a9cc3e@linuxamd.linicks.net>
[not found] ` <475A9810.4070104@anagramm.de>
2007-12-08 16:21 ` Nick Warne [this message]
2007-12-08 21:21 ` scsi_wait_scan Kconfig option Stefan Richter
2007-12-08 22:16 ` Matthew Wilcox
2007-12-07 19:39 Fw: " Nick Warne
2007-12-07 19:47 ` Matthew Wilcox
2007-12-07 21:31 ` Nick Warne
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=20071208162122.7e77601e@linuxamd.linicks.net \
--to=nick@ukfsn.org \
--cc=clemens.koller@anagramm.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;
as well as URLs for NNTP newsgroup(s).