From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Alexander Duyck <aduyck@mirantis.com>,
jbottomley@odin.com, hare@suse.de, linux-scsi@vger.kernel.org,
alexander.duyck@gmail.com, linux-kernel@vger.kernel.org,
shane.seymour@hpe.com, jthumshirn@suse.de
Subject: Re: [PATCH 0/2] scsi: Fix endless loop of ATA hard resets due to VPD reads
Date: Wed, 3 Feb 2016 08:48:09 +0200 [thread overview]
Message-ID: <20160203064808.GA10548@node.shutemov.name> (raw)
In-Reply-To: <yq1fuxamrz7.fsf@sermon.lab.mkp.net>
On Tue, Feb 02, 2016 at 09:45:48PM -0500, Martin K. Petersen wrote:
> >>>>> "Kirill" == Kirill A Shutemov <kirill@shutemov.name> writes:
>
> Kirill> I have the same problem.
>
> Kirill> Shouldn't we put quirk for that?
>
> I was hoping that Hannes' patch would do the trick so we could avoid
> blacklisting:
>
> https://patchwork.kernel.org/patch/8079011/
It didn't help me.
--
Kirill A. Shutemov
next prev parent reply other threads:[~2016-02-03 6:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 6:35 [PATCH 0/2] scsi: Fix endless loop of ATA hard resets due to VPD reads Alexander Duyck
2016-01-21 6:35 ` [PATCH 1/2] scsi: Do not attach VPD to devices that don't support it Alexander Duyck
2016-01-21 7:37 ` Hannes Reinecke
2016-01-21 17:05 ` Alexander Duyck
2016-02-02 1:22 ` Martin K. Petersen
2016-01-21 6:35 ` [PATCH 2/2] scsi: Fix RCU handling for VPD pages Alexander Duyck
2016-01-21 7:40 ` Hannes Reinecke
2016-01-21 7:40 ` Hannes Reinecke
2016-02-02 10:18 ` [PATCH 0/2] scsi: Fix endless loop of ATA hard resets due to VPD reads Kirill A. Shutemov
2016-02-03 2:45 ` Martin K. Petersen
2016-02-03 6:48 ` Kirill A. Shutemov [this message]
2016-02-03 15:27 ` Alexander Duyck
2016-02-04 2:39 ` Martin K. Petersen
2016-02-05 14:54 ` Todd Fujinaka
2016-02-10 2:09 ` Martin K. Petersen
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=20160203064808.GA10548@node.shutemov.name \
--to=kirill@shutemov.name \
--cc=aduyck@mirantis.com \
--cc=alexander.duyck@gmail.com \
--cc=hare@suse.de \
--cc=jbottomley@odin.com \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=shane.seymour@hpe.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.