From: Jean Delvare <khali@linux-fr.org>
To: Timo von Holtz <tvh@informatik.uni-kiel.de>
Cc: gregkh@suse.de, mchehab@redhat.com, d.belimov@gmail.com,
stefan.ringel@arcor.de, michel.ludwig@gmail.com,
c.pascoe@itee.uq.edu.au, ruslan@rpisarev.org.ua,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: tm6000: fixed some coding style issues
Date: Tue, 1 Feb 2011 13:23:59 +0100 [thread overview]
Message-ID: <20110201132359.4f4f9e89@endymion.delvare> (raw)
In-Reply-To: <1296559341-24438-1-git-send-email-tvh@informatik.uni-kiel.de>
Hi Timo,
On Tue, 1 Feb 2011 12:22:21 +0100, Timo von Holtz wrote:
> Fixed all of the following coding style issues:
>
> ERROR: return is not a function, parentheses are not required
> WARNING: __func__ should be used instead of gcc specific __FUNCTION__
You messed up and replaced with __func instead of __func__.
> ERROR: trailing whitespace
> ERROR: spaces required around that '=' (ctx:VxV)
> WARNING: please, no space before tabs
> WARNING: please, no spaces at the start of a line
> ERROR: space required after that ',' (ctx:VxV)
> WARNING: space prohibited between function name and open parenthesis '('
> ERROR: spaces required around that '<' (ctx:VxV)
> ERROR: spaces required around that '==' (ctx:VxV)
>
> Signed-off-by: Timo von Holtz <tvh@informatik.uni-kiel.de>
> ---
> drivers/staging/tm6000/tm6000-alsa.c | 6 +++---
> drivers/staging/tm6000/tm6000-core.c | 4 ++--
> drivers/staging/tm6000/tm6000-dvb.c | 10 +++++-----
> drivers/staging/tm6000/tm6000-i2c.c | 2 +-
> drivers/staging/tm6000/tm6000-regs.h | 2 +-
> drivers/staging/tm6000/tm6000-usb-isoc.h | 2 +-
> drivers/staging/tm6000/tm6000-video.c | 28 ++++++++++++++--------------
> drivers/staging/tm6000/tm6000.h | 4 ++--
> 8 files changed, 29 insertions(+), 29 deletions(-)
> (...)
> --- a/drivers/staging/tm6000/tm6000-usb-isoc.h
> +++ b/drivers/staging/tm6000/tm6000-usb-isoc.h
> @@ -46,5 +46,5 @@ struct usb_isoc_ctl {
> int tmp_buf_len;
>
> /* Stores already requested buffers */
> - struct tm6000_buffer *buf;
> + struct tm6000_buffer *buf;
You want one more tab to keep the struct elements aligned.
Other than that, this patch looks mostly good.
--
Jean Delvare
next prev parent reply other threads:[~2011-02-01 12:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 11:22 Timo von Holtz
2011-02-01 12:23 ` Jean Delvare [this message]
2011-02-01 12:49 Timo von Holtz
2011-02-01 13:09 ` Jean Delvare
2011-02-04 20:52 ` 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=20110201132359.4f4f9e89@endymion.delvare \
--to=khali@linux-fr.org \
--cc=c.pascoe@itee.uq.edu.au \
--cc=d.belimov@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=michel.ludwig@gmail.com \
--cc=ruslan@rpisarev.org.ua \
--cc=stefan.ringel@arcor.de \
--cc=tvh@informatik.uni-kiel.de \
/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