All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martyn Welch <martyn.welch@ge.com>
To: Gustavo Silva <silvagustavosilva@gmail.com>
Cc: devel@driverdev.osuosl.org, gregkh@suse.de,
	linux-kernel@vger.kernel.org,
	Gustavo Silva <silvagustavo@users.sourceforge.net>
Subject: Re: [PATCH 4/4] Staging: vme: devices: fix coding style issues in vme_user.c
Date: Mon, 05 Jul 2010 10:18:10 +0100	[thread overview]
Message-ID: <4C31A352.10807@ge.com> (raw)
In-Reply-To: <4C29CF3F.4070500@ge.com>

Martyn Welch wrote:
> Gustavo Silva wrote:
>   
>> This is a patch to the vme_user.c file that fixes up the following
>> issues:
>>
>> WARNING: please, no space before tabs						x 12
>> ERROR: code indent should use tabs where possible				x 15
>> WARNING: braces {} are not necessary for single statement blocks		x  2
>> WARNING: printk() should include KERN_ facility level				x  3
>> ERROR: "foo * bar" should be "foo *bar"						x  1
>> ERROR: space required before the open brace '{'					x  3
>> WARNING: space prohibited between function name and open parenthesis '('	x  1
>> ERROR: spaces required around that '=' (ctx:VxV)				x  2
>> ERROR: spaces required around that '<' (ctx:VxV)				x  2
>> ERROR: space required after that ',' (ctx:VxV)					x  3
>> ERROR: spaces required around that '?' (ctx:VxW)				x  1
>> ERROR: space required before the open parenthesis '('				x  1
>> WARNING: braces {} are not necessary for single statement blocks		x  2
>>
>>   
>>     
>
> This looks very familiar - I'm sure there was a patch already on the
> mailing list doing this, but it has some issues which I don't think were
> ever addressed. This one looks good though.
>
>   
Hmm, seems the earlier patch was fixed up and is now in linux-next, sorry.

Martyn

-- 
Martyn Welch (Principal Software Engineer)   |   Registered in England and
GE Intelligent Platforms                     |   Wales (3828642) at 100
T +44(0)127322748                            |   Barbirolli Square, Manchester,
E martyn.welch@ge.com                        |   M2 3AB  VAT:GB 927559189


  reply	other threads:[~2010-07-05  9:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-26 23:27 [PATCH 4/4] Staging: vme: devices: fix coding style issues in vme_user.c Gustavo Silva
2010-06-29 10:47 ` Martyn Welch
2010-07-05  9:18   ` Martyn Welch [this message]
2010-07-08 19:30     ` Greg KH
2010-07-08 20:29       ` Gustavo Silva

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=4C31A352.10807@ge.com \
    --to=martyn.welch@ge.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=silvagustavo@users.sourceforge.net \
    --cc=silvagustavosilva@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.