From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: James.Bottomley@steeleye.com, luben_tuikov@adaptec.com,
albertcc@tw.ibm.com, linux-scsi@vger.kernel.org
Subject: Re: [RFC] SCSI EH document
Date: Wed, 07 Sep 2005 04:04:36 -0400 [thread overview]
Message-ID: <431E9F14.7070703@pobox.com> (raw)
In-Reply-To: <20050826035326.GA13392@htj.dyndns.org>
Tejun Heo wrote:
> Hello, fellow SCSI/ATA developers.
>
> This is the first draft of SCSI EH document. This document tries to
> describe how SCSI EH works and what choirs should be done to maintain
> SCSI midlayer integrity. It's intended that this document can be used
> as reference for implementing either fine-grained EH callbacks or
> single eh_strategy_handler() callback.
>
> I'm pretty sure that I've screwed up in (hopefully) several places,
> so please correct me. Also, I have several places where I'm not sure
> or have questions, those are marked with *VERIFY* and *QUESTION*
> respectively. If you know the answer, please let me know.
>
> Thanks.
>
>
> SCSI EH
Although it's up to the SCSI maintainer ultimately, I think it would be
nice to stick this in Documentation/DocBook/ or Documentation/scsi/
Jeff
next prev parent reply other threads:[~2005-09-07 8:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 3:53 [RFC] SCSI EH document Tejun Heo
2005-08-26 21:34 ` Jeff Garzik
2005-08-29 9:14 ` Tejun Heo
2005-08-29 13:55 ` Luben Tuikov
2005-08-30 10:47 ` Tejun Heo
2005-08-30 14:50 ` Luben Tuikov
2005-08-29 18:50 ` Jeff Garzik
2005-08-29 19:49 ` Matthew Wilcox
2005-08-29 19:49 ` Jeff Garzik
2005-08-29 21:38 ` Tejun Heo
2005-08-29 22:27 ` Jeff Garzik
2005-08-26 21:36 ` Luben Tuikov
2005-09-07 8:04 ` Jeff Garzik [this message]
2005-09-07 11:22 ` Tejun Heo
2005-09-07 13:12 ` Luben Tuikov
2005-09-07 14:00 ` James Bottomley
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=431E9F14.7070703@pobox.com \
--to=jgarzik@pobox.com \
--cc=James.Bottomley@steeleye.com \
--cc=albertcc@tw.ibm.com \
--cc=htejun@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=luben_tuikov@adaptec.com \
/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).