From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Manish Rangankar <manish.rangankar@cavium.com>
Cc: martin.petersen@oracle.com, lduncan@suse.com, cleech@redhat.com,
linux-scsi@vger.kernel.org, QLogic-Storage-Upstream@cavium.com
Subject: Re: [PATCH] qla4xxx: skip error recovery in case of register disconnect.
Date: Tue, 13 Feb 2018 21:35:55 -0500 [thread overview]
Message-ID: <yq1d118pab8.fsf@oracle.com> (raw)
In-Reply-To: <20180212064841.24503-1-manish.rangankar@cavium.com> (Manish Rangankar's message of "Sun, 11 Feb 2018 22:48:41 -0800")
Manish,
> A system crashes when continuously removing/re-adding the storage
> controller.
Applied to 4.16/scsi-fixes. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2018-02-14 2:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 6:48 [PATCH] qla4xxx: skip error recovery in case of register disconnect Manish Rangankar
2018-02-12 15:05 ` Ewan D. Milne
2018-02-13 14:16 ` Tomas Henzl
2018-02-14 2:35 ` Martin K. Petersen [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=yq1d118pab8.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=QLogic-Storage-Upstream@cavium.com \
--cc=cleech@redhat.com \
--cc=lduncan@suse.com \
--cc=linux-scsi@vger.kernel.org \
--cc=manish.rangankar@cavium.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