From: James Smart <james.smart@emulex.com>
To: linux-scsi@vger.kernel.org
Subject: [PATCH 00/12] lpfc 8.3.34: Update lpfc to revision 8.3.34
Date: Tue, 14 Aug 2012 14:25:12 -0400 [thread overview]
Message-ID: <1344968712.4432.15.camel@myfc17> (raw)
This patch set updates the lpfc driver to revision 8.3.34
The patches for 8.3.34 contain:
- Add LOGO support after ABTS compliance
- Add SLI-4 V1 Capacity and Resource Descriptor support
- Fix number of IO channels to match CPUs
- Fix parameter field in CQE to mask for LOCAL_REJECT status
- Simplify BlockGuard lpfc_printf_vlog messages
- Correct typecasts for snprintf messages
- Streamline fcp underrun message printing
- Add XRI to abort handler timeout log message
- Adjust IO Channels to 1 when INTx
- Correct lock handling to eliminate reset escalation on I/O abort
- Fixed leaking memory from pci dma pool
- Update lpfc version for 8.3.34 driver release
The patches were cut against scsi.git, branch "misc", and with the
prior 8.3.33 patche set applied.
-- james s
Signed-off-by: James Smart <james.smart@emulex.com>
reply other threads:[~2012-08-14 18:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1344968712.4432.15.camel@myfc17 \
--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;
as well as URLs for NNTP newsgroup(s).