From: Pavel Machek <pavel@ucw.cz>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2][RFC] add detailed error values to block layer
Date: Fri, 26 Mar 2004 01:18:09 +0100 [thread overview]
Message-ID: <20040326001808.GA5110@elf.ucw.cz> (raw)
In-Reply-To: <4059AC04.3060109@cs.wisc.edu>
Hi!
> +enum {
> + BLK_SUCCESS,
> + BLK_ERR, /* Generic error like -EIO */
> + BLK_FATAL_DEV, /* Fatal driver error */
perhaps this should be fatal *device* error?
> + BLK_FATAL_TRNSPT, /* Fatal transport error */
> + BLK_FATAL_DRV, /* Fatal driver error */
> + BLK_RETRY_DEV, /* Device error, I/O may be retried */
> + BLK_RETRY_TRNSPT, /* Transport error, I/O may retried */
> + BLK_RETRY_DRV, /* Driver error, I/O may be retried */
> +};
> +
> +/*
> * end_request() and friends. Must be called with the request queue spinlock
> * acquired. All functions called within end_request() _must_be_ atomic.
> *
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2004-03-26 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 14:02 [PATCH 1/2][RFC] add detailed error values to block layer Mike Christie
2004-03-26 0:18 ` Pavel Machek [this message]
2004-03-26 20:49 ` Mike Christie
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=20040326001808.GA5110@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=michaelc@cs.wisc.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;
as well as URLs for NNTP newsgroup(s).