From: Greg KH <greg@kroah.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, 2 Nov 2010 06:39:43 -0700 [thread overview]
Message-ID: <20101102133943.GA2032@kroah.com> (raw)
In-Reply-To: <1288691024-25643-1-git-send-email-audun.hoem@gmail.com>
On Tue, Nov 02, 2010 at 10:43:44AM +0100, Audun Hoem wrote:
> From: Audun Hoem <audun.hoem@gmail.com>
>
> I cleaned up the coding style.
>
> 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..9d439fa 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);
> +} while (0)
Oops, no, this doesn't work, and it breaks the build. Did you test your
patch after you made it?
(hint, you need to add a few more '\' characters...)
Care to redo this and resend it?
thanks,
greg k-h
next prev parent reply other threads:[~2010-11-02 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 9:43 [PATCH] Staging: frontier: alphatrack: Fixed coding style issues Audun Hoem
2010-11-02 13:32 ` Greg KH
2010-11-02 13:39 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-11-02 15:31 [PATCH] staging: frontier: alphatrack: fixed " Audun Hoem
2010-11-02 15:37 ` Joe Perches
2010-11-02 16:06 ` Audun Hoem
2010-11-02 16:10 ` Audun Hoem
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=20101102133943.GA2032@kroah.com \
--to=greg@kroah.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.