From: "Uwe Kleine-König" <ukleinek@kernel.org>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
"Rob Herring (Arm)" <robh@kernel.org>
Cc: linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH -next] pwm: lp3943: Fix an incorrect type in lp3943_pwm_parse_dt()
Date: Fri, 9 Aug 2024 10:50:49 +0200 [thread overview]
Message-ID: <96f7b10a-e33e-4602-ab5f-4ebdac260592@kernel.org> (raw)
In-Reply-To: <20240809080523.32717-1-jiapeng.chong@linux.alibaba.com>
Hello Jiapeng,
On 8/9/24 10:05, Jiapeng Chong wrote:
> The return value from the call to of_property_count_u32_elems() is int.
> However, the return value is being assigned to an u32 variable
> 'num_outputs', so making 'num_outputs' an int.
>
> ./drivers/pwm/pwm-lp3943.c:238:6-17: WARNING: Unsigned expression compared with zero: num_outputs <= 0.
Which tool does emit this warning? My test build (with C=1 and W=1)
doesn't emit it.
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=9710
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
This problem was introduced in a commit in next:
Fixes: d6a56f3bb650 ("pwm: lp3943: Use of_property_count_u32_elems() to
get property length")
Rob: I guess this wasn't the only conversion of this type. Maybe these
others suffer from the same problem?!
> ---
> drivers/pwm/pwm-lp3943.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/pwm/pwm-lp3943.c b/drivers/pwm/pwm-lp3943.c
> index f0e94c9e5956..90b0733c00c1 100644
> --- a/drivers/pwm/pwm-lp3943.c
> +++ b/drivers/pwm/pwm-lp3943.c
> @@ -218,8 +218,7 @@ static int lp3943_pwm_parse_dt(struct device *dev,
> struct lp3943_platform_data *pdata;
> struct lp3943_pwm_map *pwm_map;
> enum lp3943_pwm_output *output;
> - int i, err, count = 0;
> - u32 num_outputs;
> + int i, err, num_outputs, count = 0;
>
> if (!node)
> return -EINVAL;
Nitpick (maybe even a subjective one):
While touching num_outputs, its scope could be reduced to the for loop.
Best regards
Uwe
next prev parent reply other threads:[~2024-08-09 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 8:05 [PATCH -next] pwm: lp3943: Fix an incorrect type in lp3943_pwm_parse_dt() Jiapeng Chong
2024-08-09 8:50 ` Uwe Kleine-König [this message]
2024-08-10 17:03 ` Uwe Kleine-König
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=96f7b10a-e33e-4602-ab5f-4ebdac260592@kernel.org \
--to=ukleinek@kernel.org \
--cc=abaci@linux.alibaba.com \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox