From: Peter Rosin <peda@lysator.liu.se>
To: Dirk Eibach <eibach@gdsys.de>
Cc: Peter Rosin <peda@axentia.se>, Jean Delvare <jdelvare@suse.de>,
Guenter Roeck <linux@roeck-us.net>,
lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: (ads1015) Handle negative conversion values correctly
Date: Fri, 19 Feb 2016 00:13:43 +0100 [thread overview]
Message-ID: <56C65027.5010403@lysator.liu.se> (raw)
In-Reply-To: <1455800872-24431-1-git-send-email-peda@lysator.liu.se>
Hi!
Sorry for the noise, but...
On 2016-02-18 14:07, Peter Rosin wrote:
> From: Peter Rosin <peda@axentia.se>
>
> Make the divisor signed as DIV_ROUND_CLOSEST is undefined for negative
> dividends when the divisor is unsigned.
>
> Signed-off-by: Peter Rosin <peda@axentia.se>
...I forgot to add this to the commit message
Cc: stable@vger.kernel.org
I also didn't explicitly mention any example platform where this
bug causes real problems; it was triggered on ARM (atmel sama5d).
Cheers,
Peter
> ---
> drivers/hwmon/ads1015.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/hwmon/ads1015.c b/drivers/hwmon/ads1015.c
> index f155b8380481..2b3105c8aed3 100644
> --- a/drivers/hwmon/ads1015.c
> +++ b/drivers/hwmon/ads1015.c
> @@ -126,7 +126,7 @@ static int ads1015_reg_to_mv(struct i2c_client *client, unsigned int channel,
> struct ads1015_data *data = i2c_get_clientdata(client);
> unsigned int pga = data->channel_data[channel].pga;
> int fullscale = fullscale_table[pga];
> - const unsigned mask = data->id == ads1115 ? 0x7fff : 0x7ff0;
> + const int mask = data->id == ads1115 ? 0x7fff : 0x7ff0;
>
> return DIV_ROUND_CLOSEST(reg * fullscale, mask);
> }
>
next prev parent reply other threads:[~2016-02-18 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 13:07 [PATCH] hwmon: (ads1015) Handle negative conversion values correctly Peter Rosin
2016-02-18 23:13 ` Peter Rosin [this message]
2016-02-19 3:16 ` Guenter Roeck
2016-02-19 22:26 ` Greg KH
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=56C65027.5010403@lysator.liu.se \
--to=peda@lysator.liu.se \
--cc=eibach@gdsys.de \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lm-sensors@lm-sensors.org \
--cc=peda@axentia.se \
/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).