From: Jonathan Cameron <jic23@kernel.org>
To: Wei Yongjun <weiyj.lk@gmail.com>
Cc: jic23@cam.ac.uk, gregkh@linuxfoundation.org,
grant.likely@secretlab.ca, rob.herring@calxeda.com,
yongjun_wei@trendmicro.com.cn, linux-iio@vger.kernel.org,
devel@driverdev.osuosl.org, devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH -next] iio: isl29018: fix to return error or 0 in isl29018_write_raw()
Date: Sat, 17 Nov 2012 10:20:36 +0000 [thread overview]
Message-ID: <50A764F4.3040008@kernel.org> (raw)
In-Reply-To: <CAPgLHd873xAvToL7reBbxmS-iEoJ9OqvjEoXf8RsG2esbTyo1A@mail.gmail.com>
On 11/08/2012 09:05 AM, Wei Yongjun wrote:
> From: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
>
> We had assigned the return value to 'ret' but ignored it when
> return from isl29018_write_raw(), it's better to return 'ret'
> instead of 0.
>
> dpatch engine is used to auto generate this patch.
> (https://github.com/weiyj/dpatch)
>
Thanks - merged to togreg branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
> Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
> ---
> drivers/staging/iio/light/isl29018.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/iio/light/isl29018.c b/drivers/staging/iio/light/isl29018.c
> index 3b03f6f..1d5b294 100644
> --- a/drivers/staging/iio/light/isl29018.c
> +++ b/drivers/staging/iio/light/isl29018.c
> @@ -356,7 +356,7 @@ static int isl29018_write_raw(struct iio_dev *indio_dev,
> }
> mutex_unlock(&chip->lock);
>
> - return 0;
> + return ret;
> }
>
> static int isl29018_read_raw(struct iio_dev *indio_dev,
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2012-11-17 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 9:05 [PATCH -next] iio: isl29018: fix to return error or 0 in isl29018_write_raw() Wei Yongjun
2012-11-17 10:20 ` 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=50A764F4.3040008@kernel.org \
--to=jic23@kernel.org \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=weiyj.lk@gmail.com \
--cc=yongjun_wei@trendmicro.com.cn \
/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).