mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: adam.latham@unisontorbay.org.uk
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
	Andrew Elwell <Andrew.Elwell@gmail.com>,
	Mithlesh Thukral <mithlesh@linsyssoft.com>,
	Svenne Krap <svenne@krap.dk>, Jiri Kosina <jkosina@suse.cz>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: Patch for wlan-ng/hfa384x_usb.c
Date: Mon, 03 May 2010 12:33:30 -0700	[thread overview]
Message-ID: <1272915210.30040.164.camel@Joe-Laptop.home> (raw)
In-Reply-To: <1272911432.1902.1.camel@ubuntu.ubuntu-domain>

On Mon, 2010-05-03 at 19:30 +0100, Adam Latham wrote:
> Subject: [PATCH] Staging: wlan-ng: fix various whitespace and 80 char issues in hfa384x_usb.c
> This is a patch to fix various whitespace and 80 character style issues found by checkpatch.pl tool
> Signed-off-by: Adam Latham <adam.latham@unisontorbay.org.uk>

Hi Adam.

> diff --git a/drivers/staging/wlan-ng/hfa384x_usb.c b/drivers/staging/wlan-ng/hfa384x_usb.c
> index 5df56f0..b7a319f 100644
> --- a/drivers/staging/wlan-ng/hfa384x_usb.c
> +++ b/drivers/staging/wlan-ng/hfa384x_usb.c
[]
> @@ -451,7 +451,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!*/

It's most common to use a space before the trailing */

> @@ -2619,7 +2619,7 @@ int hfa384x_drvr_start(hfa384x_t *hw)
>  			pr_debug("First cmd_initialize() failed (result %d),\n",
>  				 result1);
>  			pr_debug
> -			    ("but second attempt succeeded. All should be ok\n");
> +			    ("but second attempt succeeded.All should be ok\n");

Removing the space after a period here is not an improvement.



  reply	other threads:[~2010-05-03 19:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03 18:30 Adam Latham
2010-05-03 19:33 ` Joe Perches [this message]
2010-05-04 15:49   ` Greg KH

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=1272915210.30040.164.camel@Joe-Laptop.home \
    --to=joe@perches.com \
    --cc=Andrew.Elwell@gmail.com \
    --cc=adam.latham@unisontorbay.org.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --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

all inboxes | Powered by JetHome®