From: Andrew Morton <akpm@linux-foundation.org>
To: bo yang <bo.yang@lsi.com>
Cc: James.Bottomley@SteelEye.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, neela.kolli@lsi.com,
sumant.patro@lsi.com
Subject: Re: [PATCH 2/4] scsi: megaraid_sas -- add module param fast_load
Date: Tue, 3 Jul 2007 14:45:22 -0700 [thread overview]
Message-ID: <20070703144522.6b65f626.akpm@linux-foundation.org> (raw)
In-Reply-To: <1183308153.4723.8.camel@dhcp-75-197.se.lsil.com>
On Sun, 01 Jul 2007 12:42:33 -0400
bo yang <bo.yang@lsi.com> wrote:
> Driver will skip physical devices scan for the first time if the
> fast_load is set.
>
All your patches are wordwrapped and will need to be resent.
Also, there are multiple trivial errors in here, pretty much all of which
would have been detected had you run scripts/checkpatch.pl across the
diffs:
> + */
> +static unsigned int fast_load = 0;
Unneeded initialisation
> +static int megasas_slave_alloc(struct scsi_device *sdev) {
Missing newline
> + struct megasas_instance *instance ;
unneeded space
> + int tmp_fastload = fast_load;
> + instance = megasas_lookup_instance(sdev->host->host_no);
Missing blank line.
> + if (tmp_fastload && sdev->channel < MEGASAS_MAX_PD_CHANNELS) {
> + if ((sdev->id == MEGASAS_MAX_DEV_PER_CHANNEL -1) &&
> + (sdev->channel == MEGASAS_MAX_PD_CHANNELS - 1)) {
> + /* If fast load option was set and scan for last device is
> + * over, reset the fast_load flag so that during a possible
> + * next scan, devices can be made available
> + */
> + fast_load = 0;
> + }
> + return -ENXIO;
> + }
> +
> + return 0;
> +}
> +
prev parent reply other threads:[~2007-07-03 21:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-01 16:42 bo yang
2007-07-03 21:45 ` Andrew Morton [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=20070703144522.6b65f626.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=James.Bottomley@SteelEye.com \
--cc=bo.yang@lsi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=neela.kolli@lsi.com \
--cc=sumant.patro@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
all inboxes | Powered by JetHome®