From: michaelc@cs.wisc.edu
To: linux-scsi@vger.kernel.org
Subject: [RFC 0/4]: offlined device changes
Date: Thu, 19 Apr 2012 20:08:52 -0500 [thread overview]
Message-ID: <1334884136-3689-1-git-send-email-michaelc@cs.wisc.edu> (raw)
The following patches were made over scsi-misc.
The first 3 patches add a new state, SDEV_TRANSPORT_OFFLINE, which
can be used by transport classes to offline devices. This replaces
the behavior where they set some value in their check ready functions
then set the devices to running to fail IO.
The last patch has scsi-ml send a KOBJ_CHANGE event when transitioning
from SDEV_TRANSPORT_OFFLINE or SDEV_OFFLINE to SDEV_RUNNING.
next reply other threads:[~2012-04-20 1:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 1:08 michaelc [this message]
2012-04-20 1:08 ` [RFC 1/4] SCSI: add new SDEV_TRANSPORT_OFFLINE state michaelc
2012-04-20 1:08 ` [RFC 2/4] SCSI, classes, mpt2sas: have scsi_internal_device_unblock take new state michaelc
2012-04-20 1:08 ` [RFC 3/4] SCSI: remove old comment from block/unblock functions michaelc
2012-04-20 1:08 ` [RFC 4/4] SCSI: send KOBJ_CHANGE when device is set to running michaelc
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=1334884136-3689-1-git-send-email-michaelc@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--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).