public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chen Weixiang <weixiangchen@gmail.com>
To: Marek Belisko <marek.belisko@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Chen Weixiang <weixiang.chen@gmail.com>,
	Greg Donald <gdonald@gmail.com>,
	Chen Gang <gang.chen.5i5j@gmail.com>,
	Artem Fetishev <wwctrsrx@gmail.com>,
	Andrey Utkin <andrey.krieger.utkin@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/7] Remove checkpatch.pl errors from drivers/staging/ft1000
Date: Sun, 19 Oct 2014 20:59:43 +0800	[thread overview]
Message-ID: <1413723590-19690-1-git-send-email-weixiang.chen@gmail.com> (raw)

This patches remove following code style errors from drivers/staging/ft1000:

ERROR: do not initialise statics to 0 or NULL
ERROR: spaces required around that '=' (ctx:VxV)
ERROR: spaces required around that '<' (ctx:VxV)
ERROR: spaces required around that '==' (ctx:VxV)
ERROR: space required after that ',' (ctx:VxV)
ERROR: else should follow close brace '}'
ERROR: space prohibited after that open parenthesis '('
ERROR: space prohibited before that close parenthesis ')'
ERROR: space prohibited after that '&' (ctx:WxW)
ERROR: "(foo*)" should be "(foo *)"
ERROR: "foo * bar" should be "foo *bar"

Chen Weixiang (7):
  staging: ft1000: do not initialise statics to 0 or NULL
  staging: ft1000: spaces required around that '=', '<' and '=='
  staging: ft1000: space required after that ','
  staging: ft1000: else should follow close brace '}'
  staging: ft1000: space prohibited after '(' and '&', before ')'
  staging: ft1000: "(foo*)" should be "(foo *)"
  staging: ft1000: "foo * bar" should be "foo *bar"

 drivers/staging/ft1000/ft1000-pcmcia/ft1000_hw.c | 55 +++++++++++-------------
 drivers/staging/ft1000/ft1000-usb/ft1000_debug.c | 50 ++++++++++-----------
 2 files changed, 50 insertions(+), 55 deletions(-)

-- 
2.1.1


             reply	other threads:[~2014-10-19 13:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-19 12:59 Chen Weixiang [this message]
2014-10-19 12:59 ` [PATCH 1/7] staging: ft1000: do not initialise statics to 0 or NULL Chen Weixiang
2014-10-19 12:59 ` [PATCH 2/7] staging: ft1000: spaces required around that '=', '<' and '==' Chen Weixiang
2014-10-19 12:59 ` [PATCH 3/7] staging: ft1000: space required after that ',' Chen Weixiang
2014-10-19 13:27   ` Konrad Zapalowicz
2014-10-20 11:38     ` Chen Weixiang
2014-10-19 12:59 ` [PATCH 4/7] staging: ft1000: else should follow close brace '}' Chen Weixiang
2014-10-19 12:59 ` [PATCH 5/7] staging: ft1000: space prohibited after '(' and '&', before ')' Chen Weixiang
2014-10-19 12:59 ` [PATCH 6/7] staging: ft1000: "(foo*)" should be "(foo *)" Chen Weixiang
2014-10-19 12:59 ` [PATCH 7/7] staging: ft1000: "foo * bar" should be "foo *bar" Chen Weixiang

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=1413723590-19690-1-git-send-email-weixiang.chen@gmail.com \
    --to=weixiangchen@gmail.com \
    --cc=andrey.krieger.utkin@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gang.chen.5i5j@gmail.com \
    --cc=gdonald@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marek.belisko@gmail.com \
    --cc=weixiang.chen@gmail.com \
    --cc=wwctrsrx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox