From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Prakash, Sathya" <sathya.prakash@lsi.com>
Cc: linux-scsi@vger.kernel.org, eric.moore@lsi.com
Subject: Re: [PATCH 1/3] mpt fusion: Request I/O resources only when required
Date: Fri, 08 Feb 2008 11:24:15 -0600 [thread overview]
Message-ID: <1202491455.3102.47.camel@localhost.localdomain> (raw)
In-Reply-To: <20080208163534.GA20640@lsil.com>
On Fri, 2008-02-08 at 22:05 +0530, Prakash, Sathya wrote:
> This patch modifies the I/O resource allocation behavior of FUSION driver.
> The current version of driver allocates the I/O resources even if they are not required and this creates trouble in low resource environments.
> This driver now uses pci_enable_device_mem/pci_enable_device functions to differentiate the resource allocations.
>
> signed-off-by: Sathya Prakash <sathya.prakash@lsi.com>
^
Capital 'S'
The patch could also have done with a bit of checkpatch.pl love:
WARNING: Signed-off-by: is the preferred form
#58:
signed-off-by: Sathya Prakash <sathya.prakash@lsi.com>
ERROR: need space after that ',' (ctx:VxV)
#83: FILE: drivers/message/fusion/mptbase.c:1486:
+ "failed\n",ioc->name);
^
ERROR: use tabs not spaces
#84: FILE: drivers/message/fusion/mptbase.c:1487:
+ ^I^Ireturn r;$
ERROR: need space after that ',' (ctx:VxV)
#89: FILE: drivers/message/fusion/mptbase.c:1492:
+ "MEM failed\n",ioc->name);
^
ERROR: trailing whitespace
#123: FILE: drivers/message/fusion/mptbase.c:1833:
+^I^I^Ireturn 0; $
WARNING: line over 80 characters
#179: FILE: drivers/message/fusion/mptbase.h:632:
+ int bars; /* bitmask of BAR's that must be
configured */
total: 4 errors, 2 warnings, 105 lines checked
YJames
prev parent reply other threads:[~2008-02-08 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 16:35 [PATCH 1/3] mpt fusion: Request I/O resources only when required Prakash, Sathya
2008-02-08 17:24 ` James Bottomley [this message]
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=1202491455.3102.47.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=eric.moore@lsi.com \
--cc=linux-scsi@vger.kernel.org \
--cc=sathya.prakash@lsi.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