linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Murilo Opsfelder Araujo <mopsfelder@gmail.com>
To: linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Cc: gregkh@linuxfoundation.org, jic23@kernel.org,
	Murilo Opsfelder Araujo <mopsfelder@gmail.com>
Subject: [PATCH v2 0/8] staging: iio: accel: Multiple coding style fixes
Date: Mon,  4 Aug 2014 22:46:55 -0300	[thread overview]
Message-ID: <1407203223-9700-1-git-send-email-mopsfelder@gmail.com> (raw)

The following patches fix almost all warnings reported by
checkpatch.pl.

Changes from v1:
- Updated commit messages to better reflect changes.

Murilo Opsfelder Araujo (8):
  staging: iio: accel: adis16203_core.c: Add blank lines between
    declarations and code
  staging: iio: accel: adis16201_core.c: Add blank line between
    declarations and code
  staging: iio: accel: adis16204_core.c: Add blank line between
    declarations and code
  staging: iio: accel: adis16209_core.c: Add blank line between
    declarations and code
  staging: iio: accel: adis16240_core.c: Add blank line between
    declarations and code
  staging: iio: accel: lis3l02dq_core.c: Add blank lines between
    declarations and code
  staging: iio: accel: lis3l02dq_ring.c: Add blank line between
    declarations and code
  staging: iio: accel: sca3000_core.c: Add blank line between
    declarations and code

 drivers/staging/iio/accel/adis16201_core.c | 5 +++--
 drivers/staging/iio/accel/adis16203_core.c | 2 ++
 drivers/staging/iio/accel/adis16204_core.c | 1 +
 drivers/staging/iio/accel/adis16209_core.c | 1 +
 drivers/staging/iio/accel/adis16240_core.c | 1 +
 drivers/staging/iio/accel/lis3l02dq_core.c | 4 ++++
 drivers/staging/iio/accel/lis3l02dq_ring.c | 1 +
 drivers/staging/iio/accel/sca3000_core.c   | 4 +++-
 8 files changed, 16 insertions(+), 3 deletions(-)

--
2.1.0.rc1.204.gae8bc8d

             reply	other threads:[~2014-08-05  1:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05  1:46 Murilo Opsfelder Araujo [this message]
2014-08-05  1:46 ` [PATCH v2 1/8] staging: iio: accel: adis16203_core.c: Add blank lines between declarations and code Murilo Opsfelder Araujo
2014-08-05  1:46 ` [PATCH v2 2/8] staging: iio: accel: adis16201_core.c: Add blank line " Murilo Opsfelder Araujo
2014-08-05  1:46 ` [PATCH v2 3/8] staging: iio: accel: adis16204_core.c: " Murilo Opsfelder Araujo
2014-08-05  1:46 ` [PATCH v2 4/8] staging: iio: accel: adis16209_core.c: " Murilo Opsfelder Araujo
2014-08-05  1:47 ` [PATCH v2 5/8] staging: iio: accel: adis16240_core.c: " Murilo Opsfelder Araujo
2014-08-05  1:47 ` [PATCH v2 6/8] staging: iio: accel: lis3l02dq_core.c: Add blank lines " Murilo Opsfelder Araujo
2014-08-05  1:47 ` [PATCH v2 7/8] staging: iio: accel: lis3l02dq_ring.c: Add blank line " Murilo Opsfelder Araujo
2014-08-05  1:47 ` [PATCH v2 8/8] staging: iio: accel: sca3000_core.c: " Murilo Opsfelder Araujo
2014-08-05  2:02   ` Joe Perches
2014-08-05 10:24 ` [PATCH v2 0/8] staging: iio: accel: Multiple coding style fixes Dan Carpenter

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=1407203223-9700-1-git-send-email-mopsfelder@gmail.com \
    --to=mopsfelder@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).