From: Greg KH <gregkh@suse.de>
To: Alessandro Ghedini <al3xbio@gmail.com>
Cc: Andrew.Elwell@gmail.com, mithlesh@linsyssoft.com, svenne@krap.dk,
jkosina@suse.cz, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: wlan-ng: fix many style warnings in hfa384x_usb.c
Date: Wed, 21 Apr 2010 11:03:49 -0700 [thread overview]
Message-ID: <20100421180349.GA24812@suse.de> (raw)
In-Reply-To: <1271870950-19305-1-git-send-email-al3xbio@gmail.com>
On Wed, Apr 21, 2010 at 07:29:10PM +0200, Alessandro Ghedini wrote:
> This patch fixes most of the style warnings found with checkpatch.pl in the
> hfa384x_usb.c file.
>
> Signed-off-by: Alessandro Ghedini <al3xbio@gmail.com>
> ---
> drivers/staging/wlan-ng/hfa384x_usb.c | 59 ++++++++++++++++++--------------
> 1 files changed, 33 insertions(+), 26 deletions(-)
>
> diff --git a/drivers/staging/wlan-ng/hfa384x_usb.c b/drivers/staging/wlan-ng/hfa384x_usb.c
> index 5df56f0..db819be 100644
> --- a/drivers/staging/wlan-ng/hfa384x_usb.c
> +++ b/drivers/staging/wlan-ng/hfa384x_usb.c
> @@ -62,7 +62,7 @@
> *
> * hfa384x_drvr_xxxconfig An example of the drvr level abstraction. These
> * functions are wrappers for the RID get/set
> -* sequence. They call copy_[to|from]_bap() and
> +* sequence. They call copy_[to|from]_bap() and
> * cmd_access(). These functions operate on the
> * RIDs and buffers without validation. The caller
> * is responsible for that.
> @@ -351,7 +351,9 @@ static int submit_rx_urb(hfa384x_t *hw, gfp_t memflags)
> hw->rx_urb_skb = skb;
>
> result = -ENOLINK;
> - if (!hw->wlandev->hwremoved && !test_bit(WORK_RX_HALT, &hw->usb_flags)) {
> + if (!hw->wlandev->hwremoved && \
> + !test_bit(WORK_RX_HALT, &hw->usb_flags)) {
As Joe pointed out, this isn't good form.
> @@ -451,7 +453,7 @@ static void hfa384x_usb_defer(struct work_struct *data)
> if (test_bit(WORK_RX_HALT, &hw->usb_flags)) {
> int ret;
>
> - usb_kill_urb(&hw->rx_urb); /* Cannot be holding spinlock! */
> + usb_kill_urb(&hw->rx_urb); /* Cannot be holding spinlock! */
Put stuff like this on the line before, not after the code please.
thanks,
greg k-h
next prev parent reply other threads:[~2010-04-21 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 17:29 [PATCH] Staging: wlan-ng: fix many style warnings in hfa384x_usb.c Alessandro Ghedini
2010-04-21 17:59 ` Joe Perches
2010-04-21 18:03 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-22 15:49 Alessandro Ghedini
2010-04-22 17:34 ` Joe Perches
2010-04-23 9:19 ` Richard Kennedy
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=20100421180349.GA24812@suse.de \
--to=gregkh@suse.de \
--cc=Andrew.Elwell@gmail.com \
--cc=al3xbio@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mithlesh@linsyssoft.com \
--cc=svenne@krap.dk \
/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