From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
"ptikhomirov@virtuozzo.com" <ptikhomirov@virtuozzo.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"stuart.w.hayes@gmail.com" <stuart.w.hayes@gmail.com>,
"khorenko@virtuozzo.com" <khorenko@virtuozzo.com>,
"hch@lst.de" <hch@lst.de>, "hare@suse.com" <hare@suse.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"jthumshirn@suse.de" <jthumshirn@suse.de>
Subject: Re: [PATCH] Ensure that the SCSI error handler gets woken up
Date: Tue, 28 Nov 2017 15:33:45 +0000 [thread overview]
Message-ID: <1511883224.2664.3.camel@wdc.com> (raw)
In-Reply-To: <4549fca5-5d83-2e0f-195f-4460d9febc5f@virtuozzo.com>
On Tue, 2017-11-28 at 12:04 +0300, Pavel Tikhomirov wrote:
> 1-st, Stuart - thanks for adding me to CC, 2-nd Bart - no idea why you
> didn't? =)
That must have been an oversight. Sorry that I had not added you to the
Cc-list. I will add you to the Cc-list when I post the next version of this
patch.
> I don't see another way to fix these problem.
That doesn't mean that there is no other way :-) I implemented an alternative
approach yesterday and I have started testing it. I will post that patch as
soon as my tests have finished.
Bart.
next prev parent reply other threads:[~2017-11-28 15:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 1:05 [PATCH] Ensure that the SCSI error handler gets woken up Bart Van Assche
2017-11-23 8:18 ` Christoph Hellwig
2017-11-27 21:39 ` Bart Van Assche
2017-11-23 10:39 ` Johannes Thumshirn
2017-11-27 21:53 ` Stuart Hayes
2017-11-27 23:56 ` Bart Van Assche
2017-11-28 9:04 ` Pavel Tikhomirov
2017-11-28 15:33 ` Bart Van Assche [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-28 8:38 Pavel Tikhomirov
2017-11-28 8:54 Pavel Tikhomirov
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=1511883224.2664.3.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=jthumshirn@suse.de \
--cc=khorenko@virtuozzo.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ptikhomirov@virtuozzo.com \
--cc=stable@vger.kernel.org \
--cc=stuart.w.hayes@gmail.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).