public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Smart <James.Smart@Emulex.Com>
To: linux-scsi@vger.kernel.org
Subject: [PATCH 0/16] lpfc 8.1.12 :  lpfc 8.1.12 patches
Date: Wed, 25 Apr 2007 09:51:10 -0400	[thread overview]
Message-ID: <1177509070.23155.7.camel@localhost.localdomain> (raw)


Update lpfc driver to revision 8.1.12

Changes:
 - Misc bug fixes and code cleanup
 - Modify ELS abort handling to prevent double completion
 - Rework offline path to solve HBA reset issues
 - Fix unlock inside list traversal.
 - Reorganize lpfc_nlp_list() and callers to prepare for nodelist simplification
 - Round 2 of Miscellaneous fixes:
 - Fixed recovery of rport after race with dev_loss_tmo
 - Improve diagnostic messages and change local loopback message to KERN_INFO
 - Improve handling of failed ELS aborts.
 - Reference count node structures for node lifetime management.
 - Collapse discovery lists to a single node list.
 - Don't process ERATT interrupts when issuing KILL_BOARD mbx command
 - Add support for async scanning
 - Added support for 8G speed and new HBAs.
 - Update copyright year to 2007
 - Change version number to 8.1.12

-- james s



                 reply	other threads:[~2007-04-25 13:51 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=1177509070.23155.7.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