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 v2] drivers: iio: light: Fix sparse warnings
Date: Sat, 24 Sep 2016 17:38:49 +0100 [thread overview]
Message-ID: <ac0f5af8-dacf-89f7-1fde-f5c3a950be1c@kernel.org> (raw)
In-Reply-To: <20160924161455.GA8895@localhost.localdomain>
On 24/09/16 17:14, 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>
Applied to the togreg branch of iio.git and pushed out as testing for
the autobuilders to play with it.
Plenty of time for any other comments though as I won't be pushing out
togreg publicly for at least a few days.
Thanks,
Jonathan
> ---
> Changes in v2:
> * Introducing local variable to do the initial read,
> then put it in regval via be16_to_cpu call
>
> drivers/iio/light/max44000.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/light/max44000.c b/drivers/iio/light/max44000.c
> index 6511b20..a144ca3 100644
> --- a/drivers/iio/light/max44000.c
> +++ b/drivers/iio/light/max44000.c
> @@ -204,17 +204,18 @@ static int max44000_write_alspga(struct max44000_data *data, int val)
> static int max44000_read_alsval(struct max44000_data *data)
> {
> u16 regval;
> + __be16 val;
> int alstim, ret;
>
> ret = regmap_bulk_read(data->regmap, MAX44000_REG_ALS_DATA_HI,
> - ®val, sizeof(regval));
> + &val, sizeof(val));
> if (ret < 0)
> return ret;
> alstim = ret = max44000_read_alstim(data);
> if (ret < 0)
> return ret;
>
> - regval = be16_to_cpu(regval);
> + regval = be16_to_cpu(val);
>
> /*
> * Overflow is explained on datasheet page 17.
>
prev parent reply other threads:[~2016-09-24 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 16:14 [PATCH v2] drivers: iio: light: Fix sparse warnings Sandhya Bankar
2016-09-24 16:38 ` 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=ac0f5af8-dacf-89f7-1fde-f5c3a950be1c@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 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).