From: Chris Morgan <macroalpha82@gmail.com>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Cc: sre@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH] power: supply: rk817: Fix unsigned comparison with less than zero
Date: Tue, 13 Dec 2022 08:41:50 -0600 [thread overview]
Message-ID: <Y5iPLhDse826uE8O@wintermute.localhost.fail> (raw)
In-Reply-To: <20221213101904.42260-1-jiapeng.chong@linux.alibaba.com>
On Tue, Dec 13, 2022 at 06:19:04PM +0800, Jiapeng Chong wrote:
> The tmp is defined as u32 type, which results in invalid processing of
> tmp<0 in function rk817_read_or_set_full_charge_on_boot(). Therefore,
> change the tmp type to int.
Good catch, but I'm wondering if we shouldn't just drop the comparison
to less than zero? If I'm not mistaken get_unaligned_be32() only
returns unsigned integers anyway, right?
Assuming my understanding is right, we'll just drop the comparison.
Otherwise, this would be the appropriate fix.
Thank you for catching this!
Chris
>
> drivers/power/supply/rk817_charger.c:828 rk817_read_or_set_full_charge_on_boot() warn: unsigned 'tmp' is never less than zero.
> drivers/power/supply/rk817_charger.c:788 rk817_read_or_set_full_charge_on_boot() warn: unsigned 'tmp' is never less than zero.
>
> Link: https://bugzilla.openanolis.cn/show_bug.cgi?id=3444
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
> ---
> drivers/power/supply/rk817_charger.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/power/supply/rk817_charger.c b/drivers/power/supply/rk817_charger.c
> index 4f9c1c417916..7eefbcc0a4e9 100644
> --- a/drivers/power/supply/rk817_charger.c
> +++ b/drivers/power/supply/rk817_charger.c
> @@ -731,8 +731,8 @@ rk817_read_or_set_full_charge_on_boot(struct rk817_charger *charger,
> {
> struct rk808 *rk808 = charger->rk808;
> u8 bulk_reg[4];
> - u32 boot_voltage, boot_charge_mah, tmp;
> - int ret, reg, off_time;
> + u32 boot_voltage, boot_charge_mah;
> + int ret, reg, off_time, tmp;
> bool first_boot;
>
> /*
> --
> 2.20.1.7.g153144c
>
prev parent reply other threads:[~2022-12-13 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 10:19 [PATCH] power: supply: rk817: Fix unsigned comparison with less than zero Jiapeng Chong
2022-12-13 14:41 ` Chris Morgan [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=Y5iPLhDse826uE8O@wintermute.localhost.fail \
--to=macroalpha82@gmail.com \
--cc=abaci@linux.alibaba.com \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sre@kernel.org \
/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.