From: Joe Perches <joe@perches.com>
To: nick.cheng@areca.com.tw
Cc: linux-scsi@vger.kernel.org,
James.Bottomley@HansenPartnership.com,
linux-kernel@vger.kernel.org
Subject: Re: PATCH 1/3 ] SCSI: Support 1024 scatter-gather list entries and improve AP while FW trapped and behaviors of EHs
Date: Tue, 25 May 2010 22:11:29 -0700 [thread overview]
Message-ID: <1274850689.1845.11.camel@Joe-Laptop.home> (raw)
In-Reply-To: <2D7BE052D37A48D59461AB6B775FE070@areca4e4f859d4>
On Wed, 2010-05-26 at 12:55 +0800, Nick Cheng wrote:
> 1. To support 4M/1024 scatter-gather list entry, reorganize struct
> ARCMSR_CDB and struct CommandControlBlock
> 2. To modify arcmsr_probe
> 3. In order to help fix F/W issue, add the driver mode for type B card
> 4. To improve AP's behavior while F/W resets
> 5. To unify struct MessageUnit_B's members' naming in all OS drivers'
> 6. To improve error handlers, arcmsr_bus_reset(), arcmsr_abort()
> 7. To fix the arcmsr_queue_command() in bus reset stage, just let the
> commands pass down to FW, don't block
> Signed-off-by: Nick Cheng< nick.cheng@areca.com.tw >
> ---
Hi Nick.
These patches don't use normal kernel coding style.
Can you run scripts/checkpatch.pl against them please.
You've also got continuation lines like this:
+ printk(KERN_NOTICE "arcmsr%d: wait 'flush adapter cache' \
+ timeout, retry count down = %d \n", acb->host->host_no,
which are defective because of the additional white space introduced
into the format string after the line continuations.
These should written as:
printk(KERN_NOTICE "arcmsr%d: wait 'flush adapter cache' "
"timeout, retry count down = %d\n",
I did submit patches to Erich Chen <support@areca.com.tw> to fix the
some of the existing problems.
http://patchwork.kernel.org/patch/75997/
next prev parent reply other threads:[~2010-05-26 5:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 4:55 PATCH 1/3 ] SCSI: Support 1024 scatter-gather list entries and improve AP while FW trapped and behaviors of EHs Nick Cheng
2010-05-26 5:11 ` Joe Perches [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-06-18 7:39 Nick Cheng
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=1274850689.1845.11.camel@Joe-Laptop.home \
--to=joe@perches.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nick.cheng@areca.com.tw \
/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