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/6] lpfc 8.1.4 : Driver Update for bug fixes
Date: Tue, 07 Mar 2006 15:02:12 -0500	[thread overview]
Message-ID: <1141761732.25430.14.camel@localhost.localdomain> (raw)


This patch set updates the lpfc driver to revision 8.1.4, which includes
the following changes:

 - Fix Discovery processing for NPorts that change their NPortId on the fly
 - Fixed RSCN handling when a PLOGI is in retry.
 - Fixed a timer panic due to timer firing after freeing ndlp
 - Introduce lpfc_reset_barrier() function for resets on dual channel adapters
 - Two misc fixes:
   - Fix deadlock caused by return with host_lock held in lpfc_findnode_did
   - Initialize all fields of the allocated mail box structure to zero.
     Was causing some sysfs mailbox commands to fail immediately after load.
 - Change version number to 8.1.4

-- james s





             reply	other threads:[~2006-03-07 20:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-07 20:02 James Smart [this message]
2006-03-10 16:41 ` [PATCH 0/6] lpfc 8.1.4 : Driver Update for bug fixes Christoph Hellwig

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=1141761732.25430.14.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