From: Joe Perches <joe@perches.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Paul Bolle <pebolle@tiscali.nl>,
devel@driverdev.osuosl.org,
Ciaran McCormick <ciaranmccormick@gmail.com>,
gregkh@suse.de, shemminger@vyatta.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Stageing: bcm: fixed spacing coding style in led_control.c
Date: Wed, 02 Nov 2011 04:54:55 +0200 [thread overview]
Message-ID: <1320202495.15779.11.camel@Joe-Laptop> (raw)
In-Reply-To: <20111101202259.GC4682@mwanda>
On Tue, 2011-11-01 at 23:22 +0300, Dan Carpenter wrote:
> You're right that this driver needs a lot of work.
[]
> I'd prefer a series of patches:
Thanks Dan, that's a good summary of useful changes
and their best order. Couple of comments:
> [patch 1/3] Staging: bcm: fix whitespace in led_control.c
> This would address tabs vs spaces, extra prohibited spaces, and
> spaces required around certain chars. Also it would add blank lines
> between functions and between declarations and code.
And verify with git diff -w and object diffs.
> [patch 2/3] Staging: bcm: fix C99 comments in led_control.c
> This would fix the 74 ERROR: do not use C99 // comments
>
> [patch 3/3] Staging: bcm: fix braces style in led_control.c
> This would fix the 70 ERROR: that open brace { should be on the
> previous line.
I'd combine this whitespace change with 1/x myself.
> [patch 1/y] Staging: bcm: Rename "Status" to "ret" in led_control.c
> [patch 2/y] Staging: bcm: Rename CamelCase variables in led_control.c
Dan's rename_review script can help verify this as well.
https://lkml.org/lkml/2011/7/19/196
next prev parent reply other threads:[~2011-11-02 2:55 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
2011-11-01 20:22 ` Dan Carpenter
2011-11-02 2:54 ` Joe Perches [this message]
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=1320202495.15779.11.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=ciaranmccormick@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--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
Powered by JetHome