From: Yogesh Ashok Powar <yogeshp@marvell.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Lennert Buytenhek <buytenh@wantstofly.org>
Subject: Re: [PATCH] mwl8k: Fix checkpatch.pl and sparse warnings and errors
Date: Wed, 13 Apr 2011 09:29:48 +0530 [thread overview]
Message-ID: <20110413035947.GA4938@hertz.marvell.com> (raw)
In-Reply-To: <20110412202831.GC24309@tuxdriver.com>
Hi John,
Please see in-line.
On Tue, Apr 12, 2011 at 01:28:32PM -0700, John W. Linville wrote:
> On Sat, Apr 09, 2011 at 12:25:37AM +0530, Yogesh Ashok Powar wrote:
> > Fix checkpatch errors and warnings comprising of indent errors, spaces and
> > __packed warnings. Also fix 'make C = 2' warnings.
> >
> > Signed-off-by: Yogesh Ashok Powar <yogeshp@marvell.com>
> > ---
> > drivers/net/wireless/mwl8k.c | 27 +++++++++++++--------------
> > 1 files changed, 13 insertions(+), 14 deletions(-)
> >
> > diff --git a/drivers/net/wireless/mwl8k.c b/drivers/net/wireless/mwl8k.c
> > index 8913180..fb472f4 100644
> > --- a/drivers/net/wireless/mwl8k.c
> > +++ b/drivers/net/wireless/mwl8k.c
> > @@ -701,7 +701,7 @@ static int mwl8k_load_firmware(struct ieee80211_hw *hw)
> > "helper image\n", pci_name(priv->pdev));
> > return rc;
> > }
> > - msleep(5);
> > + msleep(20);
> >
> > rc = mwl8k_feed_fw_image(priv, fw->data, fw->size);
> > } else {
>
> Is this an indent error, a space, or a __packed warning??
This was checkpatch warning. The exact warning is as below
>WARNING: msleep < 20ms can sleep for up to 20ms; see Documentation/timers/timers-howto.txt
>+ msleep(5);
Thanks
Yogesh Powar
prev parent reply other threads:[~2011-04-13 4:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 18:55 [PATCH] mwl8k: Fix checkpatch.pl and sparse warnings and errors Yogesh Ashok Powar
2011-04-12 20:28 ` John W. Linville
2011-04-13 3:59 ` Yogesh Ashok Powar [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=20110413035947.GA4938@hertz.marvell.com \
--to=yogeshp@marvell.com \
--cc=buytenh@wantstofly.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).