From: Richard Kennedy <richard@rsk.demon.co.uk>
To: ehames@gmail.com
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: wlan-ng: fix coding style in hfa834x_usb.c
Date: Mon, 15 Mar 2010 09:54:45 +0000 [thread overview]
Message-ID: <4B9E03E5.70702@rsk.demon.co.uk> (raw)
In-Reply-To: <1268442475-9024-1-git-send-email-ehames@gmail.com>
On 13/03/10 01:07, ehames@gmail.com wrote:
> From: Edgardo Hames <ehames@gmail.com>
>
> This is a patch in hfa834x_usb.c to fix typedef declarations and long lines.
>
> Signed-off-by: Edgardo Hames <ehames@gmail.com>
> ---
Hi Edgardo,
Definitely a good thing to get rid of the typedefs.
> printk(KERN_ERR
> - "cmd_initialize() failed on two attempts, results %d and %d\n",
> - result1, result2);
> + "cmd_initialize() failed on two attempts,"
> + " results %d and %d\n", result1, result2);
> usb_kill_urb(&hw->rx_urb);
But I don't think you should split up the printk strings (like this one)
as it make them difficult to grep for.
> @@ -3382,8 +3382,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;
This mailing list is dead, so there's no point in still directing people
there, so you can just drop the second half of that message.
regards
Richard
prev parent reply other threads:[~2010-03-15 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-13 1:07 [PATCH] Staging: wlan-ng: fix coding style in hfa834x_usb.c ehames
2010-03-15 9:54 ` Richard Kennedy [this message]
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=4B9E03E5.70702@rsk.demon.co.uk \
--to=richard@rsk.demon.co.uk \
--cc=ehames@gmail.com \
--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