From: "Satyam Sharma" <satyam.sharma@gmail.com>
To: "James Bottomley" <James.Bottomley@steeleye.com>
Cc: "Stefan Richter" <stefanr@s5r6.in-berlin.de>,
linux-scsi@vger.kernel.org, "Simon Arlott" <simon@fire.lp0.eu>,
"Dave Jones" <davej@redhat.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
kernel-packagers@vger.kernel.org,
"Matthew Wilcox" <matthew@wil.cx>
Subject: Re: [PATCH] SCSI: Let users disable SCSI_WAIT_SCAN to be built
Date: Thu, 17 May 2007 22:32:30 +0530 [thread overview]
Message-ID: <a781481a0705171002m61bdb9e9ka53c38cbe698265e@mail.gmail.com> (raw)
In-Reply-To: <1179410407.3785.16.camel@mulgrave.il.steeleye.com>
On 5/17/07, James Bottomley <James.Bottomley@steeleye.com> wrote:
> [...]
> Please don't bother ... I really want a more considered way of fixing
> this. If everyone decides the best way is exposing this to the user,
> then this is the way to do it ... however, I still don't consider this
> argument made out yet.
Neither do I, considering that the user can switch async scanning on
at any later time with the scan=async module option. The absence
of the async scan wait module will only screw things up for him later.
But then I don't consider an argument made out yet for doing this
via a separate module in the first place. scsi_wait_scan just does
_not_ want/deserve/need to be a module.
Of course, whining is useless, and discussions on lkml tend to be
most constructive / progressive only over code, so I'll try and see
if I can learn enough of the code in there to fix a patch to do the
async scan waiting thing using some other mechanism; this
module thing seems just horribly wrong/unnecessary.
next prev parent reply other threads:[~2007-05-17 17:02 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-13 15:22 why does x86 "make defconfig" build a single, lonely module? Robert P. J. Day
2007-05-13 15:58 ` Jan Engelhardt
2007-05-13 16:06 ` Dave Jones
2007-05-13 16:10 ` James Bottomley
2007-05-13 16:18 ` James Bottomley
2007-05-13 16:30 ` Dave Jones
2007-05-14 9:35 ` Satyam Sharma
2007-05-14 9:45 ` Satyam Sharma
2007-05-14 12:00 ` Satyam Sharma
2007-05-14 12:23 ` Satyam Sharma
2007-05-14 14:31 ` James Bottomley
2007-05-15 0:41 ` Satyam Sharma
2007-05-15 11:26 ` Simon Arlott
2007-05-15 12:02 ` Asynchronous scsi scanning Matthew Wilcox
2007-05-15 16:30 ` Simon Arlott
2007-05-15 17:29 ` Matthew Wilcox
2007-05-15 21:56 ` [PATCH] SCSI: Let users disable SCSI_WAIT_SCAN to be built Stefan Richter
2007-05-16 14:43 ` Stefan Richter
2007-05-17 14:00 ` James Bottomley
2007-05-17 17:02 ` Satyam Sharma [this message]
2007-05-15 23:27 ` Asynchronous scsi scanning Satyam Sharma
2007-05-15 23:28 ` Arjan van de Ven
2007-05-15 23:49 ` Satyam Sharma
2007-05-16 2:51 ` Matthew Wilcox
2007-05-16 2:59 ` Roland Dreier
2007-05-17 17:13 ` Satyam Sharma
2007-05-17 17:20 ` Matthew Wilcox
2007-05-17 17:41 ` Satyam Sharma
2007-05-17 18:24 ` Christoph Hellwig
2007-05-17 18:47 ` Satyam Sharma
2007-05-17 18:51 ` Christoph Hellwig
2007-05-17 19:04 ` Satyam Sharma
2007-05-17 19:39 ` Matthew Wilcox
2007-05-17 19:43 ` Benjamin LaHaise
2007-05-17 21:30 ` Matthew Wilcox
2007-05-17 21:42 ` Dave Jones
2007-05-17 22:00 ` Peter Jones
2007-05-18 14:00 ` Stefan Richter
2007-05-18 5:28 ` Satyam Sharma
2007-05-18 11:24 ` Matthew Wilcox
2007-05-18 13:14 ` Satyam Sharma
2007-05-18 3:41 ` Satyam Sharma
2007-05-18 11:19 ` Matthew Wilcox
2007-05-18 13:06 ` Satyam Sharma
2007-05-17 17:32 ` sysfs makes scaling suck " Benjamin LaHaise
2007-05-17 17:45 ` James Bottomley
2007-05-17 17:49 ` Benjamin LaHaise
2007-05-19 16:30 ` Greg KH
2007-05-17 22:24 ` Peter Jones
2007-05-13 16:20 ` why does x86 "make defconfig" build a single, lonely module? Robert P. J. Day
2007-05-13 16:27 ` James Bottomley
2007-05-13 16:37 ` Robert P. J. Day
2007-05-13 17:42 ` Simon Arlott
2007-05-13 17:48 ` James Bottomley
2007-05-13 18:26 ` Simon Arlott
2007-05-13 18:45 ` Dave Jones
2007-05-13 18:45 ` James Bottomley
2007-05-14 17:29 ` Jan Engelhardt
2007-05-14 18:46 ` Alan Cox
2007-05-14 20:06 ` Jan Engelhardt
2007-05-13 16:28 ` Dave Jones
2007-05-13 20:38 ` Simon Arlott
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=a781481a0705171002m61bdb9e9ka53c38cbe698265e@mail.gmail.com \
--to=satyam.sharma@gmail.com \
--cc=James.Bottomley@steeleye.com \
--cc=davej@redhat.com \
--cc=kernel-packagers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=simon@fire.lp0.eu \
--cc=stefanr@s5r6.in-berlin.de \
/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
all inboxes | Powered by JetHome®