public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Jing Huang <huangj@brocade.com>
Cc: James.Bottomley@HansenPartnership.com, kgudipat@brocade.com,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	rvadivel@brocade.com, vravindr@brocade.com
Subject: Re: [PATCH 0/5] bfa: Brocade BFA FC SCSI driver (overview)
Date: Sat, 14 Mar 2009 22:13:28 +0100	[thread overview]
Message-ID: <20090314211328.GC3353@uranus.ravnborg.org> (raw)
In-Reply-To: <200903141952.n2EJqeHb028773@blc-10-6.brocade.com>

On Sat, Mar 14, 2009 at 12:52:40PM -0700, Jing Huang wrote:
> From: Jing Huang <huangj@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 such as 
> namming, 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.

Your submission was screwed up somehow?
You had plenty of [0/5]....

Have you ran this through checkpatch - and what is the result?
Have you run this through sparse - and what is the result?

If you have done it - please document it.
If not then please do - fix relevant issues - and document it.

	Sam

  reply	other threads:[~2009-03-14 21:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-14 19:52 [PATCH 0/5] bfa: Brocade BFA FC SCSI driver (overview) Jing Huang
2009-03-14 21:13 ` Sam Ravnborg [this message]
2009-03-14 22:48   ` Jing Huang
  -- strict thread matches above, loose matches on Subject: below --
2009-03-24  0:10 Krishna Gudipati
2009-04-02  3:32 Krishna Gudipati
2009-07-20  6:20 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=20090314211328.GC3353@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=huangj@brocade.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 \
    /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