public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Smart <James.Smart@Emulex.Com>
To: linux-scsi <linux-scsi@vger.kernel.org>
Subject: [PATCH 0/17] lpfc 8.3.2 : Update lpfc to revision 8.3.2
Date: Fri, 22 May 2009 14:50:35 -0400	[thread overview]
Message-ID: <1243018235.7729.37.camel@ogier> (raw)

This patch set updates the lpfc driver to revision 8.3.2

Emulex is releasing support for a new adapter which supports FCOE and a
next gen interface definition.  The interface definition keeps much of
the prior message content and semantics, allowing the bulk of our
discovery engine and interface into the midlayer to remain largely
intact. However, as mentioned, the hardware interface presented to the
driver, and the way it manages interrupts and message passing with the
adapter, is quite different.

This patch set adds support for this new hardware and FCOE support.
The patch set reorgs the existing code so that the bottom layers, which
interact with the hardware, can be supported in a simple form, preserving
their use by higher level software layers.  The patch set then extends
the driver with the new interface support. Lastly, there's a couple of
bug fixes and new features in this driver rev.

The changes in the 8.3.2 patch set are:
- Reorganization for SLI4 - supplied in 3 parts
- Addition of SLI4 Interface - Base Support - supplied in 6 parts
- Addition of SLI4 Interface - Queues - supplied in 2 parts
- Addition of SLI4 Interface - Mailbox handling
- Addition of SLI4 Interface - FCOE Discovery support
- Update of copyrights on modified files
- Miscellaneous Changes
- Add support for persistent vport definitions and some misc fixes
- Update the driver version to 8.3.2


-- james s

Note: converting from our own source control to this patch set was an
interesting process. I believe I logically separated the changes, but
don't be surprised to see a few random changes that perhaps aren't in
the right patch set.


 Signed-off-by: James Smart <james.smart@emulex.com>




                 reply	other threads:[~2009-05-22 18:50 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=1243018235.7729.37.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