From: Jonathan Cameron <jic23@kernel.org>
To: Murilo Opsfelder Araujo <mopsfelder@gmail.com>,
linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Cc: gregkh@linuxfoundation.org
Subject: Re: [PATCH v3 2/2] staging: iio: accel: sca3000_core.c: Adjust code to fit 80-chars limit
Date: Thu, 07 Aug 2014 10:12:43 +0100 [thread overview]
Message-ID: <53E3430B.5010209@kernel.org> (raw)
In-Reply-To: <1407370929-26949-3-git-send-email-mopsfelder@gmail.com>
On 07/08/14 01:22, Murilo Opsfelder Araujo wrote:
> Signed-off-by: Murilo Opsfelder Araujo <mopsfelder@gmail.com>
Applied to the togreg branch of iio.git.
Thanks,
Jonathan
> ---
> drivers/staging/iio/accel/sca3000_core.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/staging/iio/accel/sca3000_core.c b/drivers/staging/iio/accel/sca3000_core.c
> index bc53fedb..e4e5639 100644
> --- a/drivers/staging/iio/accel/sca3000_core.c
> +++ b/drivers/staging/iio/accel/sca3000_core.c
> @@ -506,7 +506,8 @@ static int sca3000_read_raw(struct iio_dev *indio_dev,
> mutex_unlock(&st->lock);
> return ret;
> }
> - *val = ((st->rx[0] & 0x3F) << 3) | ((st->rx[1] & 0xE0) >> 5);
> + *val = ((st->rx[0] & 0x3F) << 3) |
> + ((st->rx[1] & 0xE0) >> 5);
> }
> mutex_unlock(&st->lock);
> return IIO_VAL_INT;
>
prev parent reply other threads:[~2014-08-07 9:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 0:22 [PATCH v3 0/2] staging: iio: accel: Multiple coding style fixes Murilo Opsfelder Araujo
2014-08-07 0:22 ` [PATCH v3 1/2] staging: iio: accel: Add blank lines between declarations and code Murilo Opsfelder Araujo
2014-08-07 9:12 ` Jonathan Cameron
2014-08-07 0:22 ` [PATCH v3 2/2] staging: iio: accel: sca3000_core.c: Adjust code to fit 80-chars limit Murilo Opsfelder Araujo
2014-08-07 9:12 ` Jonathan Cameron [this message]
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=53E3430B.5010209@kernel.org \
--to=jic23@kernel.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mopsfelder@gmail.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.