linux-iio.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 2/8] staging: iio: accel: adis16201_core.c: fix coding style
Date: Thu, 31 Jul 2014 19:34:52 -0300	[thread overview]
Message-ID: <1406846098-19866-3-git-send-email-mopsfelder@gmail.com> (raw)
In-Reply-To: <1406846098-19866-1-git-send-email-mopsfelder@gmail.com>

This patch adds missing blank line after declaration and fixes lines
starting by space.

Signed-off-by: Murilo Opsfelder Araujo <mopsfelder@gmail.com>
---
 drivers/staging/iio/accel/adis16201_core.c |    5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/drivers/staging/iio/accel/adis16201_core.c b/drivers/staging/iio/accel/adis16201_core.c
index 50ba1fa..7eae5fd 100644
--- a/drivers/staging/iio/accel/adis16201_core.c
+++ b/drivers/staging/iio/accel/adis16201_core.c
@@ -111,6 +111,7 @@ static int adis16201_write_raw(struct iio_dev *indio_dev,
 	int bits;
 	s16 val16;
 	u8 addr;
+
 	switch (mask) {
 	case IIO_CHAN_INFO_CALIBBIAS:
 		switch (chan->type) {
@@ -131,8 +132,8 @@ static int adis16201_write_raw(struct iio_dev *indio_dev,
 }
 
 static const struct iio_chan_spec adis16201_channels[] = {
-  ADIS_SUPPLY_CHAN(ADIS16201_SUPPLY_OUT, ADIS16201_SCAN_SUPPLY, 0, 12),
-  ADIS_TEMP_CHAN(ADIS16201_TEMP_OUT, ADIS16201_SCAN_TEMP, 0, 12),
+	ADIS_SUPPLY_CHAN(ADIS16201_SUPPLY_OUT, ADIS16201_SCAN_SUPPLY, 0, 12),
+	ADIS_TEMP_CHAN(ADIS16201_TEMP_OUT, ADIS16201_SCAN_TEMP, 0, 12),
 	ADIS_ACCEL_CHAN(X, ADIS16201_XACCL_OUT, ADIS16201_SCAN_ACC_X,
 		BIT(IIO_CHAN_INFO_CALIBBIAS), 0, 14),
 	ADIS_ACCEL_CHAN(Y, ADIS16201_YACCL_OUT, ADIS16201_SCAN_ACC_Y,
-- 
1.7.10.4


  parent reply	other threads:[~2014-07-31 22:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-31 22:34 [PATCH 0/8] staging: iio: accel: multiple coding style fixes Murilo Opsfelder Araujo
2014-07-31 22:34 ` [PATCH 1/8] staging: iio: accel: adis16203_core.c: fix coding style Murilo Opsfelder Araujo
2014-07-31 22:34 ` Murilo Opsfelder Araujo [this message]
2014-07-31 22:34 ` [PATCH 3/8] staging: iio: accel: adis16204_core.c: " Murilo Opsfelder Araujo
2014-07-31 22:34 ` [PATCH 4/8] staging: iio: accel: adis16209_core.c: " Murilo Opsfelder Araujo
2014-07-31 22:34 ` [PATCH 5/8] staging: iio: accel: adis16240_core.c: " Murilo Opsfelder Araujo
2014-07-31 22:34 ` [PATCH 6/8] staging: iio: accel: lis3l02dq_core.c: " Murilo Opsfelder Araujo
2014-07-31 22:34 ` [PATCH 7/8] staging: iio: accel: lis3l02dq_ring.c: " Murilo Opsfelder Araujo
2014-07-31 22:34 ` [PATCH 8/8] staging: iio: accel: sca3000_core.c: " Murilo Opsfelder Araujo
2014-07-31 22:41 ` [PATCH 0/8] staging: iio: accel: multiple coding style fixes Joe Perches

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=1406846098-19866-3-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).