From: James Smart <james.smart@emulex.com>
To: linux-scsi@vger.kernel.org
Subject: [PATCH 00/21] lpfc 8.3.30: Update lpfc to revision 8.3.30
Date: Thu, 1 Mar 2012 22:33:07 -0500 [thread overview]
Message-ID: <1330659190.18500.27.camel@ogier> (raw)
This patch set updates the lpfc driver to revision 8.3.30
The patches for 8.3.30 contain:
- Make BA_ACC work on a fully qualified exchange (CR: 126289)
- Fix bug with driver not sending a LOGO with vport delete.
- Fixed port and system failure in handling SLI4 FC port function reset
- Fix driver handling of XRI Aborted CQE response
- Fix same RPI registered multiple times after HBA reset
- Fix deadlock during adapter offline request.
- Fixed missing CVL event causing round-robin FCF failover process
to stop (CR: 123367)
- Fixed SLI4 driver module load and unload test in a loop
crashes the system (CR: 126397)
- Fix resource leak when acc fails for received plogi.
- Fixed the system panic during EEH recovery
- Add additional compilation flag
- Fixed system panic when extents enabled with large number of small blocks
- Update copyright date for files modified in 2012.
- Used PCI configure space read to flush PCI funciton reset register write
- Change default DA_ID support from disabled to enabled
- Enhancements for T10 DIF debugfs error injection for DVT usage (CR: 123966)
- Fix bug with mailbox handling of REG_VFI and cable pull.
- Update copyright date for files modified in 2012.
- Added some more features for T10 DIF debugfs error injection (CR: 123966)
- Revert fix for Link Pull Causes I/O Failures
- Update lpfc to version 8.3.30
The patches were cut against scsi-misc-2.6
-- james s
Signed-off-by: Alex Iannicelli <alex.iannicelli@emulex.com>
Signed-off-by: James Smart <james.smart@emulex.com>
reply other threads:[~2012-03-02 3:33 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=1330659190.18500.27.camel@ogier \
--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).