From: Daniel Cotey <puff65537@bansheeslibrary.com>
To: Chad Williamson <chad@dahc.us>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] staging: silicom: coding style fixes for bp_proc.c
Date: Mon, 15 Oct 2012 22:38:54 -0700 [thread overview]
Message-ID: <20121016053854.GA6665@elbert.example.com> (raw)
In-Reply-To: <1350297039-8166-1-git-send-email-chad@dahc.us>
On Mon, Oct 15, 2012 at 05:30:34AM -0500, Chad Williamson wrote:
> This patch set corrects many of the coding style issues detected by
> checkpatch.pl in bp_proc.c.
>
> Chad Williamson (5):
> staging: silicom: fix whitespace in bp_proc.c
> staging: silicom: fix C99 comments in bp_proc.c
> staging: silicom: remove parentheses from return statements in bg_proc.c
> staging: silicom: remove unnecessary braces in bp_proc.c
> staging: silicom: fix explicit intialization of procfs_dir in bp_proc.c
>
> drivers/staging/silicom/bp_proc.c | 82 +++++++++++++++------------------------
> 1 file changed, 31 insertions(+), 51 deletions(-)
>
> --
> 1.7.12.2
>
Looks good to me (and as soon as asrock support pulls their head out I'll run HW tests).
Regards,
Daniel Cotey
prev parent reply other threads:[~2012-10-15 21:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 10:30 [PATCH 0/5] staging: silicom: coding style fixes for bp_proc.c Chad Williamson
2012-10-15 10:30 ` [PATCH 1/5] staging: silicom: fix whitespace in bp_proc.c Chad Williamson
2012-10-15 10:30 ` [PATCH 2/5] staging: silicom: fix C99 comments " Chad Williamson
2012-10-15 10:30 ` [PATCH 3/5] staging: silicom: remove parentheses from return statements in bg_proc.c Chad Williamson
2012-10-15 10:30 ` [PATCH 4/5] staging: silicom: remove unnecessary braces in bp_proc.c Chad Williamson
2012-10-15 10:30 ` [PATCH 5/5] staging: silicom: fix explicit intialization of procfs_dir " Chad Williamson
2012-10-16 5:38 ` Daniel Cotey [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=20121016053854.GA6665@elbert.example.com \
--to=puff65537@bansheeslibrary.com \
--cc=chad@dahc.us \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--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