From: Richard Kennedy <richard@rsk.demon.co.uk>
To: Alessandro Ghedini <al3xbio@gmail.com>
Cc: gregkh@suse.de, Andrew.Elwell@gmail.com, mithlesh@linsyssoft.com,
svenne@krap.dk, jkosina@suse.cz, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, joe@perches.com
Subject: Re: [PATCH] Staging: wlan-ng: fix many style warnings in hfa384x_usb.c
Date: Fri, 23 Apr 2010 10:19:08 +0100 [thread overview]
Message-ID: <4BD1660C.3090301@rsk.demon.co.uk> (raw)
In-Reply-To: <1271951365-17644-1-git-send-email-al3xbio@gmail.com>
On 22/04/10 16:49, 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>
> ---
> if (result2 != 0) {
> - printk(KERN_ERR
> - "cmd_initialize() failed on two attempts, results %d and %d\n",
> + printk(KERN_ERR "cmd_initialize() failed on two" \
> + "attempts, results %d and %d\n",
> result1, result2);
Hi Alessandro,
I'm not keen on splitting up printk strings. It makes it more difficult
to grep for them. It's nice and easy if you can just copy most of the
log message into grep and get to the correct bit of code.
> usb_kill_urb(&hw->rx_urb);
> goto done;
> } else {
> pr_debug("First cmd_initialize() failed (result %d),\n",
> result1);
> - pr_debug
> - ("but second attempt succeeded. All should be ok\n");
> + pr_debug("but second attempt succeeded. " \
> + "All should be ok\n");
> }
> } else if (result2 != 0) {
> printk(KERN_WARNING
> - "First cmd_initialize() succeeded, but second attempt failed (result=%d)\n",
> + "First cmd_initialize() succeeded, but second " \
> + "attempt failed (result=%d)\n",
> result2);
> printk(KERN_WARNING
> "Most likely the card will be functional\n");
> @@ -3382,8 +3384,9 @@ retry:
> * our request has been acknowledged. Odd,
> * but our OUT URB is still alive...
> */
> - pr_debug
> - ("Causality violation: please reboot Universe, or email linux-wlan-devel@lists.linux-wlan.com\n");
> + pr_debug("Causality violation: please reboot " \
> + "Universe, or email " \
> + "linux-wlan-devel@lists.linux-wlan.com\n");
> ctlx->state = CTLX_RESP_COMPLETE;
> break;
There has already been a patch for this -- I don't know if it's stuck in
Greg's queue or it got lost, but that mailing list is now dead so we can
just drop the second half of that message.
regards
Richard
next prev parent reply other threads:[~2010-04-23 9:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 15:49 [PATCH] Staging: wlan-ng: fix many style warnings in hfa384x_usb.c Alessandro Ghedini
2010-04-22 17:34 ` Joe Perches
2010-04-23 9:19 ` Richard Kennedy [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-21 17:29 Alessandro Ghedini
2010-04-21 17:59 ` Joe Perches
2010-04-21 18:03 ` 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=4BD1660C.3090301@rsk.demon.co.uk \
--to=richard@rsk.demon.co.uk \
--cc=Andrew.Elwell@gmail.com \
--cc=al3xbio@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=jkosina@suse.cz \
--cc=joe@perches.com \
--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