public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Audun Hoem <audun.hoem@gmail.com>
Cc: gregkh@suse.de, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: frontier: alphatrack: fixed coding style issues
Date: Tue, 02 Nov 2010 08:37:39 -0700	[thread overview]
Message-ID: <1288712259.7326.4.camel@Joe-Laptop> (raw)
In-Reply-To: <1288711861-3625-1-git-send-email-audun.hoem@gmail.com>

On Tue, 2010-11-02 at 16:31 +0100, Audun Hoem wrote:
> Cleaned up a macro definition and another simple style warning.
> Signed-off-by: Audun Hoem <audun.hoem@gmail.com>
> ---
>  drivers/staging/frontier/alphatrack.c |    9 ++++++---
>  1 files changed, 6 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/staging/frontier/alphatrack.c b/drivers/staging/frontier/alphatrack.c
> index ef7fbf8..6e3bd73 100644
> --- a/drivers/staging/frontier/alphatrack.c
> +++ b/drivers/staging/frontier/alphatrack.c
> @@ -88,8 +88,11 @@ MODULE_SUPPORTED_DEVICE("Frontier Designs Alphatrack Control Surface");
>  static int debug = ALPHATRACK_DEBUG;
>  
>  /* Use our own dbg macro */
> -#define dbg_info(dev, format, arg...) do \
> -    { if (debug) dev_info(dev , format , ## arg); } while (0)
> +#define dbg_info(dev, format, arg...) \
> +do { \
> +	if (debug) \
> +		dev_info(dev , format , ## arg); \

There is no need for the spaces before commas.

gcc 2.xx required a space before a comma with a trailing ##arg,
but that compiler version is no longer supported.

This should be:
	dev_info(dev, format, ##arg);

though I think using dev_dbg and getting rid of the dbg_info
macro is better.

> +} while (0)
>  
>  #define alphatrack_ocmd_info(dev, cmd, format, arg...)
>  
> @@ -769,7 +772,7 @@ static int usb_alphatrack_probe(struct usb_interface *intf,
>  	}
>  
>  	dev->write_buffer =
> -	    kmalloc(sizeof(struct alphatrack_ocmd) * true_size, GFP_KERNEL);
> +	    kmalloc(sizeof(struct alphatrack_ocmd) *true_size, GFP_KERNEL);

Not an improvement.

If checkpatch warns about this, it's a checkpatch defect.



  reply	other threads:[~2010-11-02 15:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-02 15:31 [PATCH] staging: frontier: alphatrack: fixed coding style issues Audun Hoem
2010-11-02 15:37 ` Joe Perches [this message]
2010-11-02 16:06   ` Audun Hoem
2010-11-02 16:10     ` Audun Hoem
  -- strict thread matches above, loose matches on Subject: below --
2010-11-02  9:43 [PATCH] Staging: frontier: alphatrack: Fixed " Audun Hoem
2010-11-02 13:32 ` Greg KH
2010-11-02 13:39 ` 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=1288712259.7326.4.camel@Joe-Laptop \
    --to=joe@perches.com \
    --cc=audun.hoem@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /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