From: James Smart <James.Smart@Emulex.Com>
To: Michael Reed <mdr@sgi.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
Gary Hagensen <gwh@sgi.com>, Jeremy Higdon <jeremy@sgi.com>,
"Moore, Eric Dean" <Eric.Moore@lsil.com>,
"Shirron, Stephen" <Stephen.Shirron@lsil.com>
Subject: Re: [PATCH] scsi_wq (fc transport) thread hang
Date: Thu, 11 May 2006 12:24:39 -0400 [thread overview]
Message-ID: <44636547.6060700@emulex.com> (raw)
In-Reply-To: <445A296B.3060501@sgi.com>
Everyone,
FYI - please note that this patch has been NACK'd.
Michael continued to work on this issue and has realized that this
patch is not the correct one. I will be posting an updated patch for
this issue shortly.
-- james s
next prev parent reply other threads:[~2006-05-11 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 16:18 [PATCH] scsi_wq (fc transport) thread hang Michael Reed
2006-05-11 16:24 ` James Smart [this message]
[not found] <4458E8ED.2060704@sgi.com>
[not found] ` <4458F4BA.3000009@sgi.com>
[not found] ` <445B5195.5050001@emulex.com>
2006-05-05 13:53 ` Michael Reed
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=44636547.6060700@emulex.com \
--to=james.smart@emulex.com \
--cc=Eric.Moore@lsil.com \
--cc=Stephen.Shirron@lsil.com \
--cc=gwh@sgi.com \
--cc=jeremy@sgi.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mdr@sgi.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).