mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jing Huang <huangj@brocade.com>
To: James.Bottomley@HansenPartnership.com
Cc: kgudipat@brocade.com, linux-kernel@vger.kernel.org,
	linux-scsi@vger.kernel.org, rvadivel@brocade.com,
	vravindr@brocade.com, xmzhang@brocade.com
Subject: [PATCH 0/6] bfa: Brocade BFA FC SCSI driver (overview)
Date: Tue, 21 Jul 2009 16:06:44 -0700	[thread overview]
Message-ID: <200907212306.n6LN6i6j007166@swe57.brocade.com> (raw)

From: Jing Huang <huangj@brocade.com>

I have to resubmit the patch I posted a few days ago. It seems that one of
the patches I submitted never showed up in LKML (I tried twice), 
I suspect it got rejected due to its size. Now I am retrying by splitting that
patch into two.

In this submission, we completed all the pening works in our last submission
in April, including:
1) Added support of Brocade PCIe FCOE HBA.
2) Cleaned up FC state machine code.
3) Completed implementing code review comments received from the open source
community.

It contains a serial of 6 patches generated using 2.6.30.1 kernel. Here is
a brief description of each patch:

[PATCH 1/6]: SCSI LLD driver code, module init/exit, PCI and SCSI host entry
points, interrupt handler, and sysfs interface etc. 

[PATCH 2/6]: Hardware/FW access code.

[PATCH 3/6]: FC state machines.

[PATCH 4/6]: Common header files shared by linux driver,
hardware/FW access code, FC state machines.

[PATCH 5/6]: Updated Kconfig and Makefile for driver/scsi, and Makefile
for bfa driver 

[PATCH 6/6]: Updated MAINTAINER file.

Signed-off-by: Jing Huang <huangj@brocade.com>
---

                 reply	other threads:[~2009-07-21 23:06 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=200907212306.n6LN6i6j007166@swe57.brocade.com \
    --to=huangj@brocade.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=kgudipat@brocade.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rvadivel@brocade.com \
    --cc=vravindr@brocade.com \
    --cc=xmzhang@brocade.com \
    /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

all inboxes | Powered by JetHome®