From: Joe Perches <joe@perches.com>
To: "Philip J. Kelleher" <pjk1939@linux.vnet.ibm.com>
Cc: axboe@kernel.dk, linux-kernel@vger.kernel.org,
brking@linux.vnet.ibm.com, josh.h.morris@us.ibm.com
Subject: Re: [PATCHv2 1/1] block: IBM RamSan 70/80 driver fixes.
Date: Tue, 19 Feb 2013 08:57:09 -0800 [thread overview]
Message-ID: <1361293029.2360.4.camel@joe-AO722> (raw)
In-Reply-To: <20130219164811.GA21104@oc6784271780.ibm.com>
On Tue, 2013-02-19 at 10:48 -0600, Philip J. Kelleher wrote:
> From: Philip J Kelleher <pjk1939@linux.vnet.ibm.com>
>
> This patch include a few driver fixes for the IBM RamSan 70/80 driver.
trivial comments:
> diff -uprN -X linux-block-vanilla/Documentation/dontdiff linux-block-vanilla/drivers/block/rsxx/config.c linux-block/drivers/block/rsxx/config.c
[]
> @@ -161,6 +161,17 @@ irqreturn_t rsxx_isr(int irq, void *pdat
> }
>
> /*----------------- Card Event Handler -------------------*/
> +static char *rsxx_card_state_to_str(unsigned int state)
static const char *
> +{
> + static char *state_strings[] = {
static const char * const state_strings[] = {
> + "Unknown", "Shutdown", "Starting", "Formatting",
> + "Uninitialized", "Good", "Shutting Down",
> + "Fault", "Read Only Fault", "dStroying"
> + };
[]
> @@ -390,8 +391,13 @@ static int __issue_creg_rw(struct rsxx_c
> if (st)
> return st;
>
> + /*
> + * This timeout is neccessary for unresponsive hardware. The additional
One "c" in necessary
> + * 20 seconds to used to guarantee that each cregs requests has time to
> + * complete.
> + */
> timeout = msecs_to_jiffies((CREG_TIMEOUT_MSEC *
> - card->creg_ctrl.q_depth) + 20000);
> + card->creg_ctrl.q_depth) + 20000);
The alignment was nicer before this change.
Still using unnecessary parentheses.
next prev parent reply other threads:[~2013-02-19 16:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 16:48 Philip J. Kelleher
2013-02-19 16:57 ` Joe Perches [this message]
2013-02-19 17:33 ` Philip J. Kelleher
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=1361293029.2360.4.camel@joe-AO722 \
--to=joe@perches.com \
--cc=axboe@kernel.dk \
--cc=brking@linux.vnet.ibm.com \
--cc=josh.h.morris@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pjk1939@linux.vnet.ibm.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
all inboxes | Powered by JetHome®