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: iio: tsl2x7x_core: fix multiple coding style issues
Date: Sat, 12 Mar 2016 16:19:19 +0800 [thread overview]
Message-ID: <cover.1457769810.git.eraretuya@gmail.com> (raw)
Eliminate majority of checkpatch issues on tsl2x7x_core.c
---
This patch was already submitted before but somehow got lost in the queue. Probably because I did not send the v2 right away or some other reason.
Original submission can be found here:
https://groups.google.com/forum/#!topicsearchin/outreachy-kernel/subject$3Aiio$3A$20AND$20subject$3Atsl2x7x_core$3A$20AND$20after$3A2016$2F02$2F09/outreachy-kernel/SgWiOEpe17Q
Eva Rachel Retuya (5):
staging: iio: tsl2x7x_core: adjust alignment to match open parenthesis
staging: iio: tsl2x7x_core: use preferred comment style
staging: iio: tsl2x7x_core: remove space after a cast
staging: iio: tsl2x7x_core: add spaces around operators
staging: iio: tsl2x7x_core: add blank line after struct declaration
drivers/staging/iio/light/tsl2x7x_core.c | 211 ++++++++++++++++++-------------
1 file changed, 122 insertions(+), 89 deletions(-)
--
1.9.1
next reply other threads:[~2016-03-12 8:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-12 8:19 Eva Rachel Retuya [this message]
2016-03-12 8:19 ` [PATCH v2 1/5] staging: iio: tsl2x7x_core: adjust alignment to match open parenthesis Eva Rachel Retuya
2016-03-12 8:19 ` [PATCH v2 2/5] staging: iio: tsl2x7x_core: use preferred comment style Eva Rachel Retuya
2016-03-12 8:19 ` [PATCH v2 3/5] staging: iio: tsl2x7x_core: remove space after a cast Eva Rachel Retuya
2016-03-12 8:19 ` [PATCH v2 4/5] staging: iio: tsl2x7x_core: add spaces around operators Eva Rachel Retuya
2016-03-12 8:19 ` [PATCH v2 5/5] staging: iio: tsl2x7x_core: add blank line after struct declaration 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.1457769810.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.