From: Jeremy Linton <jlinton@tributary.com>
To: "james.smart@emulex.com" <james.smart@emulex.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 17/18] lpfc 8.3.42: Fixed issue of task management commands having a fixed timeout
Date: Mon, 9 Sep 2013 09:43:08 -0500 [thread overview]
Message-ID: <522DDE7C.1020008@tributary.com> (raw)
In-Reply-To: <522C82DF.2000305@emulex.com>
On 9/8/2013 8:59 AM, James Smart wrote:
> The other issue - we seem to have missed your prior post. I'll look into it
> shortly.
Thanks,
Those patches were the result of various error injection test cases we were
performing. The ones that come to mind were, hung sequences, TM rejects,
failures to respond to the TM, etc.
prev parent reply other threads:[~2013-09-09 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 16:22 [PATCH 17/18] lpfc 8.3.42: Fixed issue of task management commands having a fixed timeout James Smart
2013-09-06 18:38 ` Jeremy Linton
2013-09-08 13:59 ` James Smart
2013-09-09 14:43 ` Jeremy Linton [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=522DDE7C.1020008@tributary.com \
--to=jlinton@tributary.com \
--cc=james.smart@emulex.com \
--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).