From: James Smart <James.Smart@Emulex.Com>
To: linux-scsi@vger.kernel.org
Subject: [PATCH 0/3] lpfc 8.2.8 v2 : recut of conflicting 8.2.8 patches
Date: Sun, 07 Sep 2008 11:51:46 -0400 [thread overview]
Message-ID: <1220802706.6747.9.camel@localhost.localdomain> (raw)
This patch set is reworked versions of 8.2.8 patches that were failing
due to conflicts with the target busy and transport disrupted changes.
patch1 resolves the target_busy vs transport_disrupted status
patch2 is a recut of:
[PATCH 12/15] lpfc 8.2.8 : Add sysfs control of target queue depth handling
patch3 is a recut of:
[PATCH 14/15] lpfc 8.2.8 : Add statistical reporting control and additional
fc vendor events
-- james s
next reply other threads:[~2008-09-07 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-07 15:51 James Smart [this message]
2008-09-07 15:57 ` [PATCH 0/3] lpfc 8.2.8 v2 : recut of conflicting 8.2.8 patches James Smart
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=1220802706.6747.9.camel@localhost.localdomain \
--to=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