From: Fabio Falzoi <fabio.falzoi84@gmail.com>
To: gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Fabio Falzoi <fabio.falzoi84@gmail.com>
Subject: [PATCH v3 0/6] Staging: rts5139: Fix coding style
Date: Tue, 22 Apr 2014 23:22:58 +0200 [thread overview]
Message-ID: <1398201784-7602-1-git-send-email-fabio.falzoi84@gmail.com> (raw)
Fix some coding style issues in rts51x.c (from rts5139 module).
Changes in v3:
* removed all the Out Of Memory messages
* redefined pr_fmt to add a prefix to each pr_<level>.
Changes in v2:
* patch splitted to have just one specific coding style issue fixed at a time
Fabio Falzoi (6):
Staging: rts5139: Camel case labels replaced
Staging: rts5139: Fixed multi-line code alignment
Staging: rts5139: Splitted one-line multiple assignment
Staging: rts5139: Use standard pr_<level> prefixing
Staging: rts5139: Removed OOM messages
Staging: rts5139: More appropriate use of sizeof operand
drivers/staging/rts5139/rts51x.c | 125 ++++++++++++++++++---------------------
1 file changed, 57 insertions(+), 68 deletions(-)
--
1.9.1
next reply other threads:[~2014-04-22 21:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 21:22 Fabio Falzoi [this message]
2014-04-22 21:22 ` [PATCH v3 1/6] Staging: rts5139: Camel case labels replaced Fabio Falzoi
2014-04-22 22:03 ` Dan Carpenter
2014-04-22 21:23 ` [PATCH v3 2/6] Staging: rts5139: Fixed multi-line code alignment Fabio Falzoi
2014-04-22 21:23 ` [PATCH v3 3/6] Staging: rts5139: Splitted one-line multiple assignment Fabio Falzoi
2014-04-22 21:23 ` [PATCH v3 4/6] Staging: rts5139: Use standard pr_<level> prefixing Fabio Falzoi
2014-04-22 22:07 ` Dan Carpenter
2014-04-22 22:10 ` Dan Carpenter
2014-04-22 21:23 ` [PATCH v3 5/6] Staging: rts5139: Removed OOM messages Fabio Falzoi
2014-04-22 21:23 ` [PATCH v3 6/6] Staging: rts5139: More appropriate use of sizeof operand Fabio Falzoi
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=1398201784-7602-1-git-send-email-fabio.falzoi84@gmail.com \
--to=fabio.falzoi84@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®