From: Krishna Gudipati <kgudipat@brocade.com>
To: James.Bottomley@HansenPartnership.com
Cc: huangj@brocade.com, kgudipat@brocade.com,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
rvadivel@brocade.com, vravindr@brocade.com
Subject: [PATCH 0/5] bfa: Brocade BFA FC SCSI driver (overview)
Date: Mon, 23 Mar 2009 17:10:09 -0700 [thread overview]
Message-ID: <200903240010.n2O0A9vp013492@blc-10-2.brocade.com> (raw)
From: Krishna Chaitanya Gudipati <kgudipat@brocade.com>
This is the an interim submission of Brocade BFA FC SCSI Driver for code review.
We moved FC protocol/port state machine part of the driver to the firmware to
make the driver simpler. We also implemented the code review comments received
from last submission which includes: 1) replaced bfa specific list management
routines by standard linux list implemetation. 2) Other minor fixes to naming,
Makefile, kconfig etc.
Please note that this driver is still not fully functioning. We expect to do
anoher submssion next week after we complete all the changes.
It contains a serial of 5 patches generated using 2.6.29-rc8 kernel. Here is
a brief description of each patch:
[PATCH 1/5]: 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/5]: Hardware/FW access code. All files start with "bfa_" prefix.
[PATCH 3/5]: Common header files shared by linux driver specific and
hardware/FW access code.
[PATCH 4/5]: Updated Kconfig and Makefile for driver/scsi, and Makefile
for bfa driver.
[PATCH 5/5]: Updated MAINTAINER file.
Signed-off-by: Krishna Chaitanya Gudipati <kgudipat@brocade.com>
---
next reply other threads:[~2009-03-24 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 0:10 Krishna Gudipati [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-07-20 6:20 Jing Huang
2009-04-02 3:32 Krishna Gudipati
2009-03-14 19:52 Jing Huang
2009-03-14 21:13 ` Sam Ravnborg
2009-03-14 22:48 ` Jing Huang
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=200903240010.n2O0A9vp013492@blc-10-2.brocade.com \
--to=kgudipat@brocade.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=huangj@brocade.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rvadivel@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®