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/14] lpfc 8.3.0 :  Update lpfc to rev 8.3.0
Date: Fri, 5 Dec 2008 09:44:28 -0500	[thread overview]
Message-ID: <1228488268.3927.0.camel@ogier> (raw)

Update lpfc driver to revision 8.3.0

Includes the following changes :
 - Rework RSCN netlink event to send entire RSCN payload
 - Add support for Power Management Suspend/Resume operations
 - Add kernel-doc function headers to lpfc_scsi.c
 - Fix system crash due to uninitialized node access
 - Fix multiple NPIV issues
 - Added 3 small features and improve PCI EEH support
 - Don't assume HBA supports Interrupt Enable Block
 - Fix several minor issues
 - Added active interrupt test for enabling MSI/MSI-X/INTx
 - Fix some memory handling issues
 - Add BlockGuard support (T10-DIF) Part 1
 - Add BlockGuard support (T10-DIF) Part 2
 - Hook lpfc's debugfs into Kconfig
 - Update driver version to 8.3.0

James, I'm hoping this can be queued up for 2.6.29 inclusion. Patches
are cut against scsi-misc-2.6

-- james s





                 reply	other threads:[~2008-12-05 14:44 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=1228488268.3927.0.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