From: Eva Rachel Retuya <eraretuya@gmail.com>
To: outreachy-kernel@googlegroups.com
Cc: Eva Rachel Retuya <eraretuya@gmail.com>
Subject: [PATCH v2 0/5] staging: fbtft: fb_ili9xxx.c: fix multiple coding style issues
Date: Fri, 12 Feb 2016 15:39:25 +0800 [thread overview]
Message-ID: <cover.1455260992.git.eraretuya@gmail.com> (raw)
Address checkpatch WARNING and CHECK issues on the fb_ili9xxx series of files.
Change in v2:
* Modify subject lines to avoid duplicates from a different patchset.
Eva Rachel Retuya (5):
staging: fbtft: Modify block comments based on kernel coding style
staging: fbtft: Fix alignment to match open parenthesis
staging: fbtft: Insert blank line after function declaration
staging: fbtft: Delete blank line after '{' brace
staging: fbtft: Remove the use of CamelCase
drivers/staging/fbtft/fb_ili9163.c | 103 +++++++++++++++++++------------------
drivers/staging/fbtft/fb_ili9320.c | 13 ++---
drivers/staging/fbtft/fb_ili9325.c | 81 +++++++++++++++--------------
drivers/staging/fbtft/fb_ili9340.c | 8 +--
drivers/staging/fbtft/fb_ili9341.c | 19 +++----
drivers/staging/fbtft/fb_ili9481.c | 7 ++-
6 files changed, 117 insertions(+), 114 deletions(-)
--
1.9.1
next reply other threads:[~2016-02-12 7:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 7:39 Eva Rachel Retuya [this message]
2016-02-12 7:39 ` [PATCH v2 1/5] staging: fbtft: Modify block comments based on kernel coding style Eva Rachel Retuya
2016-02-12 7:39 ` [PATCH v2 2/5] staging: fbtft: Fix alignment to match open parenthesis Eva Rachel Retuya
2016-02-12 7:39 ` [PATCH v2 3/5] staging: fbtft: Insert blank line after function declaration Eva Rachel Retuya
2016-02-12 7:39 ` [PATCH v2 4/5] staging: fbtft: Delete blank line after '{' brace Eva Rachel Retuya
2016-02-12 7:39 ` [PATCH v2 5/5] staging: fbtft: Remove the use of CamelCase Eva Rachel Retuya
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.1455260992.git.eraretuya@gmail.com \
--to=eraretuya@gmail.com \
--cc=outreachy-kernel@googlegroups.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.