public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	Lee Jones <lee.jones@linaro.org>, Olof Johansson <olof@lixom.net>,
	bleung@chromium.org
Cc: martinez.javier@gmail.com, Guenter Roeck <groeck@chromium.org>,
	Gwendal Grignou <gwendal@chromium.org>,
	linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
	rtc-linux@googlegroups.com
Subject: Re: [PATCH 2/7] iio: cros_ec_sensors: Fix return value to get raw and calibbias data.
Date: Sat, 25 Mar 2017 15:07:19 +0000	[thread overview]
Message-ID: <bac2ea92-bc32-cdcf-5fce-30909a05784e@kernel.org> (raw)
In-Reply-To: <20170324174407.25401-3-enric.balletbo@collabora.com>

On 24/03/17 17:44, Enric Balletbo i Serra wrote:
> The cros_ec_sensors_read function must return the type of value on all
> cases. This was always true except for RAW and CALIBBIAS data which
> returned an error or 0. This patch just fixes the mistake I introduced
> when submitting the series.
> 
> Fixes: commit c14dca07a31d (iio: cros_ec_sensors: add ChromeOS EC
> Contiguous Sensors driver)
> 
> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Applied to the fixes-togreg branch of iio.git.

Thanks,

Jonathan
> ---
> 
>   This is another FIX, so would be interesting see it merged in this release
> cycle too. Like the above patch can be picked independently of the other
> patches and should go through IIO Jonathan's Cameron tree.
> 
>  drivers/iio/common/cros_ec_sensors/cros_ec_sensors.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/iio/common/cros_ec_sensors/cros_ec_sensors.c b/drivers/iio/common/cros_ec_sensors/cros_ec_sensors.c
> index d6c372b..c17596f 100644
> --- a/drivers/iio/common/cros_ec_sensors/cros_ec_sensors.c
> +++ b/drivers/iio/common/cros_ec_sensors/cros_ec_sensors.c
> @@ -61,7 +61,7 @@ static int cros_ec_sensors_read(struct iio_dev *indio_dev,
>  		ret = st->core.read_ec_sensors_data(indio_dev, 1 << idx, &data);
>  		if (ret < 0)
>  			break;
> -
> +		ret = IIO_VAL_INT;
>  		*val = data;
>  		break;
>  	case IIO_CHAN_INFO_CALIBBIAS:
> @@ -76,7 +76,7 @@ static int cros_ec_sensors_read(struct iio_dev *indio_dev,
>  		for (i = CROS_EC_SENSOR_X; i < CROS_EC_SENSOR_MAX_AXIS; i++)
>  			st->core.calib[i] =
>  				st->core.resp->sensor_offset.offset[i];
> -
> +		ret = IIO_VAL_INT;
>  		*val = st->core.calib[idx];
>  		break;
>  	case IIO_CHAN_INFO_SCALE:
> 

  reply	other threads:[~2017-03-25 15:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-24 17:44 [PATCH 0/7] mfd: cros-ec: Some fixes and improvements Enric Balletbo i Serra
2017-03-24 17:44 ` [PATCH 1/7] mfd: cros-ec: Fix host command buffer size Enric Balletbo i Serra
2017-04-03 14:23   ` Lee Jones
2017-04-03 14:30     ` Lee Jones
2017-04-03 15:12       ` Enric Balletbo i Serra
2017-04-04  8:37         ` Lee Jones
2017-04-04  8:36   ` Lee Jones
2017-03-24 17:44 ` [PATCH 2/7] iio: cros_ec_sensors: Fix return value to get raw and calibbias data Enric Balletbo i Serra
2017-03-25 15:07   ` Jonathan Cameron [this message]
2017-03-24 17:44 ` [PATCH 3/7] iio: cros_ec_sensors: Use devm to setup the triggered buffer Enric Balletbo i Serra
2017-03-25 15:09   ` Jonathan Cameron
2017-03-24 17:44 ` [PATCH 4/7] mfd: cros_ec: Get rid of cros_ec_check_features from cros_ec_dev Enric Balletbo i Serra
2017-03-25 15:22   ` Jonathan Cameron
2017-03-25 15:24     ` Jonathan Cameron
2017-03-27 12:42     ` Lee Jones
2017-04-02 10:41       ` Jonathan Cameron
2017-03-24 17:44 ` [PATCH 5/7] mfd: cros_ec: Introduce RTC commands and events definitions Enric Balletbo i Serra
2017-03-24 17:44 ` [PATCH 6/7] rtc: cros-ec: add cros-ec-rtc driver Enric Balletbo i Serra
2017-03-24 17:44 ` [PATCH 7/7] mfd: cros_ec: add RTC as mfd subdevice Enric Balletbo i Serra
2017-04-03 14:25   ` Lee Jones
2017-04-03 15:06     ` Enric Balletbo i Serra
2017-04-04  8:38       ` Lee Jones

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=bac2ea92-bc32-cdcf-5fce-30909a05784e@kernel.org \
    --to=jic23@kernel.org \
    --cc=bleung@chromium.org \
    --cc=enric.balletbo@collabora.com \
    --cc=groeck@chromium.org \
    --cc=gwendal@chromium.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martinez.javier@gmail.com \
    --cc=olof@lixom.net \
    --cc=rtc-linux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox