From: Mike Anderson <andmike@us.ibm.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: David Brownell <david-b@pacbell.net>,
Linux SCSI list <linux-scsi@vger.kernel.org>
Subject: Re: Bugs in scsi system, need help to fix
Date: Mon, 14 Apr 2003 13:40:38 -0700 [thread overview]
Message-ID: <20030414204038.GF4162@beaverton.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0304141017580.827-100000@ida.rowland.org>
Alan Stern [stern@rowland.harvard.edu] wrote:
> Thanks, Mike. Is it safe to assume that a combined fix for all these
> problems will be posted in the next few weeks, as part of the
> hot-unplugging development effort?
The fix for the scsi_eh_lock_done problem I am testing a patch now and
hopefully will have it out for others to test later today.
The fix / removal of scsi_check_device_busy will be part of the scsi
host remove / offline patches.
-andmike
--
Michael Anderson
andmike@us.ibm.com
prev parent reply other threads:[~2003-04-14 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3E982DDE.7010002@pacbell.net>
2003-04-12 20:10 ` Bugs in scsi system, need help to fix Alan Stern
2003-04-14 6:23 ` Mike Anderson
2003-04-14 14:20 ` Alan Stern
2003-04-14 20:40 ` Mike Anderson [this message]
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=20030414204038.GF4162@beaverton.ibm.com \
--to=andmike@us.ibm.com \
--cc=david-b@pacbell.net \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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