From: Jonathan Cameron <jic23@kernel.org>
To: Su Hui <suhui@nfschina.com>
Cc: lars@metafoo.de, jean-baptiste.maneyrol@tdk.com,
chenhuiz@axis.com, andy.shevchenko@gmail.com,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] iio: imu: inv_mpu6050: return callee's error code rather than -EINVAL
Date: Sun, 26 Nov 2023 17:07:00 +0000 [thread overview]
Message-ID: <20231126170700.550d20e7@jic23-huawei> (raw)
In-Reply-To: <20231030020752.67630-1-suhui@nfschina.com>
On Mon, 30 Oct 2023 10:07:53 +0800
Su Hui <suhui@nfschina.com> wrote:
> regmap_bulk_write()/regmap_bulk_read() return zero or negative error
> code, return the callee's error code is better than '-EINVAL'.
Thanks and fully agree - though one small tweak I made whilst applying is mentioned
below.
Applied to the togreg branch of iio.git and pushed out as testing for 0-day
to see if we missed anything.
>
> Signed-off-by: Su Hui <suhui@nfschina.com>
> ---
> drivers/iio/imu/inv_mpu6050/inv_mpu_core.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c b/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c
> index a9a5fb266ef1..5ded0781797c 100644
> --- a/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c
> +++ b/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c
> @@ -572,7 +572,7 @@ static int inv_mpu6050_sensor_set(struct inv_mpu6050_state *st, int reg,
> ind = (axis - IIO_MOD_X) * 2;
> result = regmap_bulk_write(st->map, reg + ind, &d, sizeof(d));
> if (result)
> - return -EINVAL;
> + return result;
>
> return 0;
I tweaked this to go further
return regmap_bulk_write();
> }
> @@ -586,7 +586,7 @@ static int inv_mpu6050_sensor_show(struct inv_mpu6050_state *st, int reg,
> ind = (axis - IIO_MOD_X) * 2;
> result = regmap_bulk_read(st->map, reg + ind, &d, sizeof(d));
> if (result)
> - return -EINVAL;
> + return result;
> *val = (short)be16_to_cpup(&d);
>
> return IIO_VAL_INT;
prev parent reply other threads:[~2023-11-26 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 2:07 Su Hui
2023-11-26 17:07 ` 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=20231126170700.550d20e7@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=chenhuiz@axis.com \
--cc=jean-baptiste.maneyrol@tdk.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suhui@nfschina.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
all inboxes | Powered by JetHome®