From: Christoph Hellwig <hch@infradead.org>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-block@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/2] scsi: convert unrecovered read error to -EILSEQ
Date: Wed, 19 Apr 2017 22:37:11 -0700 [thread overview]
Message-ID: <20170420053711.GA10381@infradead.org> (raw)
In-Reply-To: <1491221029-1609-1-git-send-email-dmonakhov@openvz.org>
Looks like I won't get the major error status changes into 4.12,
so let's go with these patches for now:
Reviewed-by: Christoph Hellwig <hch@lst.de>
prev parent reply other threads:[~2017-04-20 5:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 12:03 [PATCH 1/2] scsi: convert unrecovered read error to -EILSEQ Dmitry Monakhov
2017-04-03 12:03 ` [PATCH 2/2] block: Improve error handling verbosity Dmitry Monakhov
2017-04-20 5:37 ` Christoph Hellwig
2017-04-04 6:57 ` [PATCH 1/2] scsi: convert unrecovered read error to -EILSEQ Christoph Hellwig
2017-04-20 5:37 ` Christoph Hellwig [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=20170420053711.GA10381@infradead.org \
--to=hch@infradead.org \
--cc=dmonakhov@openvz.org \
--cc=linux-block@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;
as well as URLs for NNTP newsgroup(s).