mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jing Huang <huangj@brocade.com>
To: James.Bottomley@HansenPartnership.com
Cc: huangj@brocade.com, linux-kernel@vger.kernel.org,
	linux-scsi@vger.kernel.org, rvadivel@brocade.com,
	srayas@brocade.com, vravindr@brocade.com
Subject: [PATCH 0/6] bfa: Brocade BFA FC SCSI driver submission (2nd try)
Date: Thu, 25 Sep 2008 17:50:47 -0700	[thread overview]
Message-ID: <200809260050.m8Q0oltC027096@swe37.brocade.com> (raw)

From: Jing Huang <huangj@brocade.com>

This is the initial submission of Brocade BFA FC SCSI Driver to the
upstream kernel. The following 1-6 patches contain the driver source for
Brocade 8G Fibre Channel to PCIe HBA and other supporting files for kernel
inclusion. Brocade Fibre Channel HBA driver, also called as BFA driver, is
a SCSI lower layer driver. It interfaces with SCSI mid layer, and controls
Brocade FC controller through its firmware API. BFA driver supports fabric,
P2P and autotopolgy. It runs at 1/2/4/8G and auto link speed. It also
supports features such as sysfs interface, NPIV, and PCI hotplug etc.     

Here is a brief description of the patches included in this submission:

[PATCH 1/6]: Linux driver specific code, things such as module load/unload,
PCI probe/release, interrupt handler, and sysfs interface etc. All the files
start with "bfad_" prefix.

[PATCH 2/6]: Hardware/FW access code. All files start with "bfa_" prefix.

[PATCH 3/6]: Common header files shared by linux driver specific and
hardware/FW access code.

[PATCH 4/6]: Updated Kconfig and Makefile for driver/scsi, and new Makefile
and Kconfig file for bfa driver 

[PATCH 5/6]: Document for Brocade specific sysfs interface for HBA management.

[PATCH 6/6]: Update MAINTAINER file.

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

                 reply	other threads:[~2008-09-26  0:51 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=200809260050.m8Q0oltC027096@swe37.brocade.com \
    --to=huangj@brocade.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rvadivel@brocade.com \
    --cc=srayas@brocade.com \
    --cc=vravindr@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®