Date: Sat, 14 Mar 2009 22:13:28 +0100
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)
Message-ID: <20090314211328.GC3353@uranus.ravnborg.org>
References: <200903141952.n2EJqeHb028773@blc-10-6.brocade.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200903141952.n2EJqeHb028773@blc-10-6.brocade.com>
User-Agent: Mutt/1.4.2.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1852
Lines: 45

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/