From: Jonathan Cameron <jic23@kernel.org>
To: Sandhya Bankar <bankarsandhya512@gmail.com>,
knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
linux-iio@vger.kernel.org
Subject: Re: [PATCH] drivers: iio: light: Fix sparse warnings
Date: Sat, 24 Sep 2016 16:21:01 +0100 [thread overview]
Message-ID: <9c0fb251-3d55-9da9-0f12-71e2c26231e4@kernel.org> (raw)
In-Reply-To: <20160924121211.GA12546@localhost.localdomain>
On 24/09/16 13:12, Sandhya Bankar wrote:
> Fixing below warnings:
>
> drivers/iio/light/max44000.c:217:18: warning: cast to restricted __be16
> drivers/iio/light/max44000.c:217:18: warning: cast to restricted __be16
> drivers/iio/light/max44000.c:217:18: warning: cast to restricted __be16
> drivers/iio/light/max44000.c:217:18: warning: cast to restricted __be16
>
> Signed-off-by: Sandhya Bankar <bankarsandhya512@gmail.com>
This is really just papering over the problem.
A better solution would be to introduce a __be16 local variable to do
the initial read into. Then put it in regval via that be16_to_cpu
call.
Jonathan
> ---
> drivers/iio/light/max44000.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/light/max44000.c b/drivers/iio/light/max44000.c
> index 6511b20..1ea9af9 100644
> --- a/drivers/iio/light/max44000.c
> +++ b/drivers/iio/light/max44000.c
> @@ -214,7 +214,7 @@ static int max44000_read_alsval(struct max44000_data *data)
> if (ret < 0)
> return ret;
>
> - regval = be16_to_cpu(regval);
> + be16_to_cpus(®val);
>
> /*
> * Overflow is explained on datasheet page 17.
>
next prev parent reply other threads:[~2016-09-24 15:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 12:12 [PATCH] drivers: iio: light: Fix sparse warnings Sandhya Bankar
2016-09-24 15:21 ` Jonathan Cameron [this message]
2016-09-24 18:51 ` Alison Schofield
2016-09-24 19:55 ` [Outreachy kernel] " Julia Lawall
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=9c0fb251-3d55-9da9-0f12-71e2c26231e4@kernel.org \
--to=jic23@kernel.org \
--cc=bankarsandhya512@gmail.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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.