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/11] lpfc 8.3.38: Update lpfc to revision 8.3.38
Date: Fri, 1 Mar 2013 16:34:59 -0500	[thread overview]
Message-ID: <1362173699.8283.16.camel@myfc17> (raw)

This patch set updates the lpfc driver to revision 8.3.38

The patches for 8.3.38 contain:

- Fixed NMI watch dog panic's when resetting the hba.
- Fixed degraded performance after cable pulls
- Fixed bsg timeout handling issues that would result in crashes
- Fixed deadlock condition in FCF round robin handling
- Fixed async FCF modified event to in-use FCF failure to trigger recovery
- Fixed OXID reuse issue.
- Fixed PT2PT bring up problem for FC SLI4.
- Fixed circular locking dependency and inconsistent lock state issues
- Fix default value for lpfc_enable_rrq.
- Fixed potential mis-interpretation of READ_TOPOLOGY reserved fields
- Update lpfc version for 8.3.38 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-03-01 21:36 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=1362173699.8283.16.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