From: Mike Anderson <andmike@us.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Patrick Mansfield <patmans@us.ibm.com>,
Alan Stern <stern@rowland.harvard.edu>,
James Bottomley <James.Bottomley@steeleye.com>,
Matthew Dharm <mdharm-scsi@one-eyed-alien.net>,
USB Storage List <usb-storage@one-eyed-alien.net>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: Notify about errors during initialization
Date: Tue, 6 Jan 2004 11:04:52 -0800 [thread overview]
Message-ID: <20040106190452.GB2119@beaverton.ibm.com> (raw)
In-Reply-To: <20040106180832.A19009@infradead.org>
Christoph Hellwig [hch@infradead.org] wrote:
> On Tue, Jan 06, 2004 at 10:08:14AM -0800, Mike Anderson wrote:
> > > Because some drivers (like the ieee1394) don't want scanning to happen.
> > > They can easily chose that by not sending a scan event.
> > >
> >
> > Couldn't the user space also set the policy to scan or not scan? It
> > would seem that user space would be more flexible and not need a new
> > api (Just do not call scsi_scan_host).
>
> For ieee1394 scanning doesn't make any sense, so I don't see why it should
> scan at all.
>
> And I don't understand that API argument at all. With my suggestion
> scsi_scan_host would be changed to send the hotplug even - not change in
> API at all.
ok, I was reading two replies back when you mentioned
"scsi_scan_host_parallel". I re-read the last reply and see that
scsi_scan_host would just send a scan event.
-andmike
--
Michael Anderson
andmike@us.ibm.com
next prev parent reply other threads:[~2004-01-06 19:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031207051634.GB21951@one-eyed-alien.net>
2003-12-08 16:15 ` Notify about errors during initialization Alan Stern
2004-01-05 2:10 ` Matthew Dharm
2004-01-05 22:04 ` Alan Stern
2004-01-05 22:13 ` Christoph Hellwig
2004-01-05 23:32 ` Mike Anderson
2004-01-06 16:17 ` Christoph Hellwig
2004-01-06 17:15 ` Patrick Mansfield
2004-01-06 17:18 ` Christoph Hellwig
2004-01-06 18:08 ` Mike Anderson
2004-01-06 18:08 ` Christoph Hellwig
2004-01-06 19:04 ` Mike Anderson [this message]
2004-01-06 18:07 ` Sysfs attribute file for max_sectors Alan Stern
2004-01-06 18:23 ` James Bottomley
2004-01-06 19:31 ` Alan Stern
2004-01-06 19:47 ` James Bottomley
2004-01-07 16:16 ` PATCH: (as168) " Alan Stern
2004-01-06 21:11 ` Patrick Mansfield
2004-01-06 21:14 ` Jens Axboe
2004-01-06 22:00 ` Alan Stern
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=20040106190452.GB2119@beaverton.ibm.com \
--to=andmike@us.ibm.com \
--cc=James.Bottomley@steeleye.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mdharm-scsi@one-eyed-alien.net \
--cc=patmans@us.ibm.com \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@one-eyed-alien.net \
/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.