linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Matt Ranostay <matt.ranostay@intel.com>, adriana.reus@intel.com
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: imu: mpu6050: remove trailing whitespaces
Date: Sun, 21 Feb 2016 21:12:22 +0000	[thread overview]
Message-ID: <56CA2836.6000908@kernel.org> (raw)
In-Reply-To: <1455775103-18130-1-git-send-email-matt.ranostay@intel.com>

On 18/02/16 05:58, Matt Ranostay wrote:
> removed several trailing whitespaces before assignment operations
> 
> Signed-off-by: Matt Ranostay <matt.ranostay@intel.com>
Applied with some fuzz from other recent patches on this driver.

Jonathan
> ---
>  drivers/iio/imu/inv_mpu6050/inv_mpu_core.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c b/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c
> index 225860016fed..cbc8c74d4692 100644
> --- a/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c
> +++ b/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c
> @@ -244,7 +244,7 @@ static int inv_mpu6050_read_raw(struct iio_dev *indio_dev,
>  				if (result)
>  					goto error_read_raw;
>  			}
> -			ret =  inv_mpu6050_sensor_show(st, st->reg->raw_gyro,
> +			ret = inv_mpu6050_sensor_show(st, st->reg->raw_gyro,
>  						chan->channel2, val);
>  			if (!st->chip_config.gyro_fifo_enable ||
>  					!st->chip_config.enable) {
> @@ -567,7 +567,7 @@ static int inv_mpu6050_validate_trigger(struct iio_dev *indio_dev,
>  		.type = _type,                                        \
>  		.modified = 1,                                        \
>  		.channel2 = _channel2,                                \
> -		.info_mask_shared_by_type =  BIT(IIO_CHAN_INFO_SCALE), \
> +		.info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE), \
>  		.info_mask_separate = BIT(IIO_CHAN_INFO_RAW),         \
>  		.scan_index = _index,                                 \
>  		.scan_type = {                                        \
> @@ -587,7 +587,7 @@ static const struct iio_chan_spec inv_mpu_channels[] = {
>  	 */
>  	{
>  		.type = IIO_TEMP,
> -		.info_mask_separate =  BIT(IIO_CHAN_INFO_RAW)
> +		.info_mask_separate = BIT(IIO_CHAN_INFO_RAW)
>  				| BIT(IIO_CHAN_INFO_OFFSET)
>  				| BIT(IIO_CHAN_INFO_SCALE),
>  		.scan_index = -1,
> 


      reply	other threads:[~2016-02-21 21:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-18  5:58 [PATCH] iio: imu: mpu6050: remove trailing whitespaces Matt Ranostay
2016-02-21 21: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=56CA2836.6000908@kernel.org \
    --to=jic23@kernel.org \
    --cc=adriana.reus@intel.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=matt.ranostay@intel.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 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).