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 6/8] staging: iio: accel: lis3l02dq_core.c: Add blank lines between declarations and code
Date: Mon, 4 Aug 2014 22:47:01 -0300 [thread overview]
Message-ID: <1407203223-9700-7-git-send-email-mopsfelder@gmail.com> (raw)
In-Reply-To: <1407203223-9700-1-git-send-email-mopsfelder@gmail.com>
This patch adds missing blank line between declarations and code,
satisfying checkpatch.pl.
Signed-off-by: Murilo Opsfelder Araujo <mopsfelder@gmail.com>
---
drivers/staging/iio/accel/lis3l02dq_core.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/staging/iio/accel/lis3l02dq_core.c b/drivers/staging/iio/accel/lis3l02dq_core.c
index 898653c..f5e145c 100644
--- a/drivers/staging/iio/accel/lis3l02dq_core.c
+++ b/drivers/staging/iio/accel/lis3l02dq_core.c
@@ -212,6 +212,7 @@ static int lis3l02dq_write_thresh(struct iio_dev *indio_dev,
int val, int val2)
{
u16 value = val;
+
return lis3l02dq_spi_write_reg_s16(indio_dev,
LIS3L02DQ_REG_THS_L_ADDR,
value);
@@ -226,6 +227,7 @@ static int lis3l02dq_write_raw(struct iio_dev *indio_dev,
int ret = -EINVAL, reg;
u8 uval;
s8 sval;
+
switch (mask) {
case IIO_CHAN_INFO_CALIBBIAS:
if (val > 255 || val < -256)
@@ -302,6 +304,7 @@ static ssize_t lis3l02dq_read_frequency(struct device *dev,
struct iio_dev *indio_dev = dev_to_iio_dev(dev);
int ret, len = 0;
s8 t;
+
ret = lis3l02dq_spi_read_reg_8(indio_dev,
LIS3L02DQ_REG_CTRL_1_ADDR,
(u8 *)&t);
@@ -565,6 +568,7 @@ static int lis3l02dq_read_event_config(struct iio_dev *indio_dev,
u8 val;
int ret;
u8 mask = (1 << (chan->channel2*2 + (dir == IIO_EV_DIR_RISING)));
+
ret = lis3l02dq_spi_read_reg_8(indio_dev,
LIS3L02DQ_REG_WAKE_UP_CFG_ADDR,
&val);
--
2.1.0.rc1.204.gae8bc8d
next prev parent 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 [PATCH v2 0/8] staging: iio: accel: Multiple coding style fixes Murilo Opsfelder Araujo
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 ` Murilo Opsfelder Araujo [this message]
2014-08-05 1:47 ` [PATCH v2 7/8] staging: iio: accel: lis3l02dq_ring.c: " 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-7-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).