From: Anchal Jain <anchalj109@gmail.com>
To: gregkh@linuxfoundation.org
Cc: jic23@kernel.org, lars@metafoo.de, outreachy-kernel@googlegroups.com
Subject: [PATCH v4 1/2] staging: iio: cdc: ad7152: Add blank line after function to increase readability
Date: Tue, 4 Oct 2016 12:52:45 +0530 [thread overview]
Message-ID: <20161004072236.GA4047@life-desktop> (raw)
Add a blank line after the function to increase the readability of the code.
Signed-off-by: Anchal Jain <anchalj109@gmail.com>
---
changes in v4-
-modify patch title
drivers/staging/iio/cdc/ad7152.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/staging/iio/cdc/ad7152.c b/drivers/staging/iio/cdc/ad7152.c
index 1962052..f9767e9 100644
--- a/drivers/staging/iio/cdc/ad7152.c
+++ b/drivers/staging/iio/cdc/ad7152.c
@@ -134,6 +134,7 @@ static inline ssize_t ad7152_start_calib(struct device *dev,
mutex_unlock(&indio_dev->mlock);
return len;
}
+
static ssize_t ad7152_start_offset_calib(struct device *dev,
struct device_attribute *attr,
const char *buf,
@@ -142,6 +143,7 @@ static ssize_t ad7152_start_offset_calib(struct device *dev,
return ad7152_start_calib(dev, attr, buf, len,
AD7152_CONF_MODE_OFFS_CAL);
}
+
static ssize_t ad7152_start_gain_calib(struct device *dev,
struct device_attribute *attr,
const char *buf,
@@ -317,6 +319,7 @@ out:
mutex_unlock(&indio_dev->mlock);
return ret;
}
+
static int ad7152_read_raw(struct iio_dev *indio_dev,
struct iio_chan_spec const *chan,
int *val, int *val2,
@@ -470,6 +473,7 @@ static const struct iio_chan_spec ad7152_channels[] = {
BIT(IIO_CHAN_INFO_SCALE),
}
};
+
/*
* device probe and remove
*/
--
1.9.1
next reply other threads:[~2016-10-04 7:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 7:22 Anchal Jain [this message]
2016-10-09 7:53 ` [PATCH v4 1/2] staging: iio: cdc: ad7152: Add blank line after function to increase readability Jonathan Cameron
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=20161004072236.GA4047@life-desktop \
--to=anchalj109@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--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.