linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Giedrius Statkevicius <giedrius.statkevicius@gmail.com>
To: gregkh@linuxfoundation.org
Cc: micky_ching@realsil.com.cn, fabio.falzoi84@gmail.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] staging: rts5208: clean up coding style in rtsx_chip.c
Date: Sat,  4 Oct 2014 00:53:08 +0300	[thread overview]
Message-ID: <cover.1412372293.git.giedrius.statkevicius@gmail.com> (raw)

From: Giedrius Statkevičius <giedrius.statkevicius@gmail.com>

This patch set is a general code style clean up for rtsx_chip.c. After
this patch set checkpatch.pl without --strict doesn't complain anything
about at all and with --strict it only complains about unmatched
parantheses in those few places where I can't fix them because I don't
have the hardware to test the bigger changes nor do I have enough
experience to make such bigger changes flawlessly.

(Sorry for littering the mailing list. You can delete my other threads.
I somehow accidentaly managed to reply to my older thread. This is
really embarassing.)

Giedrius Statkevičius (5):
  staging: rts5208: combine ifs where possible
  staging: rts5208: get rid of Camel Case, remove unneeded lines and
    parantheses
  staging: rts5208: align divided lines to opening paranthesis
  staging: rts5208: divide lines to make them less than 80 characters
    long
  staging: rts5208: use ternary operators to reduce indentation level

 drivers/staging/rts5208/rtsx_chip.c | 322 +++++++++++++++---------------------
 1 file changed, 136 insertions(+), 186 deletions(-)

-- 
2.1.2

             reply	other threads:[~2014-10-03 21:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-03 21:53 Giedrius Statkevicius [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-10-03 21:31 [PATCH 0/5] staging: rts5208: clean up coding style in rtsx_chip.c Giedrius Statkevicius
2014-10-03 20:27 Giedrius Statkevicius

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=cover.1412372293.git.giedrius.statkevicius@gmail.com \
    --to=giedrius.statkevicius@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=fabio.falzoi84@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=micky_ching@realsil.com.cn \
    /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;
as well as URLs for NNTP newsgroup(s).