From: James Smart <james.smart@emulex.com>
To: linux-scsi@vger.kernel.org
Subject: [PATCH 0/22] lpfc 8.3.39: Update lpfc to revision 8.3.39
Date: Wed, 17 Apr 2013 20:14:22 -0400 [thread overview]
Message-ID: <1366244062.1513.0.camel@myfc17> (raw)
This patch set updates the lpfc driver to revision 8.3.39
The patches for 8.3.39 contain:
-
- Fixed VPI allocation issues after firmware dump is performed
- Fixed BlockGuard error reporting
- Remove driver dependency on HZ
- Fixed pt2pt and loop discovery problems on topology changes.
- Fix driver issues with large lpfc_sg_seg_cnt values
- Fix driver issues with large s/g lists for BlockGuard
- Doorbell formation information logged in dual-chute mode WQ and RQ setup
- Fix driver issues with SCSI Host reset
- Fix lpfc_fcp_look_ahead module parameter
- Fixed crash when processing bsg's sg list with high memory pages
- Reduced spinlock contention on SCSI buffer list
- Fixed BlockGuard to take advantage of rdprotect/wrprotect info when available
- Fixed deadlock between hbalock and nlp_lock use.
- Fixed bad book keeping in posting els sgls to port
- Fixed not returning FAILED status when SCSI invoking host reset handler
failed
- Fixed system panic during EEH recovery due to midlayer acting on
outstanding I/O
- Fixed iocb flags not being reset for scsi commands.
- Fixed driver vector mapping to CPU affinity
- Add log message when completes with clean address bit set to zero
- Reduced tmo value set to FLOGI WQE for quick recovery from FLOGI sequence
timeout
- Fixed driver handling of CLEAR_LA with NPIV enabled causing SID=0 frames out
- Update lpfc version for 8.3.39 driver release
The patches were cut against scsi.git, branch "misc".
-- james s
Signed-off-by: James Smart <james.smart@emulex.com>
reply other threads:[~2013-04-18 0:14 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=1366244062.1513.0.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