From: James Bottomley <James.Bottomley@steeleye.com>
To: Mike Anderson <andmike@us.ibm.com>
Cc: Andrey Borzenkov <arvidjaar@mail.ru>,
Linux Kernel <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: 2.6.1: media change check fails for busy unplugged device
Date: 31 Jan 2004 08:53:48 -0500 [thread overview]
Message-ID: <1075517314.1655.8.camel@mulgrave> (raw)
In-Reply-To: <20040129093051.GA1556@beaverton.ibm.com>
On Thu, 2004-01-29 at 04:30, Mike Anderson wrote:
> The sdev->online flag was left as is when the device state model was
> update as we where overloading the meaning on this flag. I believe James
> last statement on this was that we need to merge this in at some point
> (correct James?).
Yes, I've just been extremely reticent about doing it because it
complicates the state model. However, I'll get off my backside and see
if I can come up with a model update including it.
James
prev parent reply other threads:[~2004-01-31 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 18:41 2.6.1: media change check fails for busy unplugged device Andrey Borzenkov
2004-01-19 23:36 ` Mike Anderson
2004-01-26 19:16 ` Andrey Borzenkov
2004-01-29 9:30 ` Mike Anderson
2004-01-31 13:53 ` James Bottomley [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=1075517314.1655.8.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=andmike@us.ibm.com \
--cc=arvidjaar@mail.ru \
--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