From: James Bottomley <James.Bottomley@SteelEye.com>
To: Sumant Patro <sumantp@lsil.com>
Cc: linux-scsi@vger.kernel.org, akpm@osdl.org, hch@lst.de,
linux-kernel@vger.kernel.org
Subject: Re: [Patch 1/6] megaraid_sas: FW transition and q size changes
Date: Wed, 04 Oct 2006 12:56:11 -0500 [thread overview]
Message-ID: <1159984571.3437.22.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <1159903729.5618.7.camel@dumbo>
On Tue, 2006-10-03 at 12:28 -0700, Sumant Patro wrote:
> Resubmitting with one addition (item f mentioned below)
>
> This patch has the following enhancements :
> a. handles new transition states of FW to support controller hotplug.
> b. It reduces by 1 the maximum cmds that the driver may send to FW.
> c. Sends "Stop Processing" cmd to FW before returning failure from reset routine
> d. Adds print in megasas_transition routine
> e. Sends "RESET" flag to FW to do a soft reset of controller
> to move from Operational to Ready state.
> f. Sending correct pointer (cmd->sense) to pci_pool_free
>
> This patch has been generated on latest scsi-misc git.
>
> Signed-off-by: Sumant Patro <Sumant.Patro@lsil.com>
Every one of these patches had extra whitespace at the end of several
lines. This is a sample from the first patch:
Adds trailing whitespace.
.dotest/patch:21: if (fw_state != MFI_STATE_READY)
Adds trailing whitespace.
.dotest/patch:44: case MFI_STATE_BOOT_MESSAGE_PENDING:
Adds trailing whitespace.
.dotest/patch:85: * Reduce the max supported cmds by 1. This is
to ensure that the
Could you please try to ensure it doesn't happen in future ... it's time
consuming to clean it all up again.
Thanks,
James
next prev parent reply other threads:[~2006-10-04 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 19:28 [Patch 1/6] megaraid_sas: FW transition and q size changes Sumant Patro
2006-10-04 17:56 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-05 0:44 Patro, Sumant
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=1159984571.3437.22.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sumantp@lsil.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