From: Anatoly Stepanov <drivengroove@gmail.com>
To: linux-fbdev@vger.kernel.org
Subject: [PATCH 00/11] staging: sm750fb: fix checkpatch issues
Date: Sun, 28 Jun 2015 23:43:53 +0000 [thread overview]
Message-ID: <1435535044-22042-1-git-send-email-drivengroove@gmail.com> (raw)
This patch series fixes chekpatch.pl errors in sm750fb.
Anatoly Stepanov (11):
staging: sm750fb: replace spaces with tabs
staging: sm750fb: remove trailing whitespaces
staging: sm750fb: insert space between ')' and '{'
staging: sm750fb: insert space before open parenthesis
staging: sm750fb: fix indentation of pointer operator
staging: sm750fb: put open brace on the previous line
staging: sm750fb: fix indentation in 'else' statements
staging: sm750fb: fix 'switch and case' indentation
staging: sm750fb: remove assignment from if condition
staging: sm750fb: fix open brace in function declaration
staging: sm750fb: add required spaces around C operators
drivers/staging/sm750fb/sm750_hw.c | 403 ++++++++++++++++++-------------------
1 file changed, 198 insertions(+), 205 deletions(-)
--
2.1.0
reply other threads:[~2015-06-28 23:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1435535044-22042-1-git-send-email-drivengroove@gmail.com \
--to=drivengroove@gmail.com \
--cc=linux-fbdev@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