From: Paul Bolle <pebolle@tiscali.nl>
To: Ciaran McCormick <ciaranmccormick@gmail.com>
Cc: gregkh@suse.de, shemminger@vyatta.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Stageing: bcm: fixed spacing coding style in led_control.c
Date: Tue, 01 Nov 2011 12:07:45 +0100 [thread overview]
Message-ID: <1320145665.14409.149.camel@x61.thuisdomein> (raw)
In-Reply-To: <1320144259-22339-1-git-send-email-ciaranmccormick@gmail.com>
Stageing? And you might as well drop the filename from the summary. By
the way, are the other files (if any) of this driver any better (I
haven't checked)?
On Tue, 2011-11-01 at 10:44 +0000, Ciaran McCormick wrote:
> ---
> drivers/staging/bcm/led_control.c | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/bcm/led_control.c b/drivers/staging/bcm/led_control.c
> index 16e939f..28c3382 100644
> --- a/drivers/staging/bcm/led_control.c
> +++ b/drivers/staging/bcm/led_control.c
> @@ -5,8 +5,8 @@
>
> static B_UINT16 CFG_CalculateChecksum(B_UINT8 *pu8Buffer, B_UINT32 u32Size)
> {
> - B_UINT16 u16CheckSum=0;
> - while(u32Size--) {
> + B_UINT16 u16CheckSum = 0;
> + while (u32Size--) {
> u16CheckSum += (B_UINT8)~(*pu8Buffer);
I'd say this line might need a space after the cast.
> pu8Buffer++;
> }
> @@ -16,7 +16,7 @@ BOOLEAN IsReqGpioIsLedInNVM(PMINI_ADAPTER Adapter, UINT gpios)
> {
> INT Status ;
> Status = (Adapter->gpioBitMap & gpios) ^ gpios ;
You missed the space before the semicolons here.
> - if(Status)
> + if (Status)
> return FALSE;
> else
> return TRUE;
But, more importantly, why only do whitespace related stuff? Almost
every second word apparently needs to be restyled here. Is doing just
whitespace related stuff worthwhile? (This is not a rhetorical question.
I'm actually wondering what Greg prefers).
Paul Bolle
next prev parent reply other threads:[~2011-11-01 11:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 10:44 Ciaran McCormick
2011-11-01 11:07 ` Paul Bolle [this message]
2011-11-01 20:22 ` Dan Carpenter
2011-11-02 2:54 ` Joe Perches
2011-11-02 6:26 ` Dan Carpenter
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=1320145665.14409.149.camel@x61.thuisdomein \
--to=pebolle@tiscali.nl \
--cc=ciaranmccormick@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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®