public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Wang Ming <machel@vivo.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	linux-kernel@vger.kernel.org, opensource.kernel@vivo.com
Subject: Re: [PATCH v1] drivers:base:Fix unsigned compared with less than zero
Date: Wed, 14 Jun 2023 15:33:33 +0100	[thread overview]
Message-ID: <20230614-passcode-stimulate-70eecb6d81d2@spud> (raw)
In-Reply-To: <20230614133549.3774-1-machel@vivo.com>

[-- Attachment #1: Type: text/plain, Size: 2495 bytes --]

Hey,

On Wed, Jun 14, 2023 at 09:35:36PM +0800, Wang Ming wrote:
> The return value of the of_count_cache_leaves() is long.
> However, the return value is being assigned to an unsigned
> long variable 'leaves',so making 'leaves' to long.

But you actually made it an int?

> silence the warning:
> ./drivers/base/cacheinfo.c:300:5-11: WARNING: Unsigned expression
> compared with zero: leaves > 0

I'm dumb, why is comparing an unsigned value with zero a problem in and
of itself? Zero is a valid value for an unsigned type, no?

If you actually look at the function, it only returns positive, non-zero
values anyway, so returning an int is a bit pointless, as are the
checks, no?

> 
> Signed-off-by: Wang Ming <machel@vivo.com>
> ---
>  drivers/base/cacheinfo.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/base/cacheinfo.c b/drivers/base/cacheinfo.c
> index cbae8be1f..7280d5cb3 100644
> --- a/drivers/base/cacheinfo.c
> +++ b/drivers/base/cacheinfo.c
> @@ -289,7 +289,8 @@ int init_of_cache_level(unsigned int cpu)
>         struct cpu_cacheinfo *this_cpu_ci = get_cpu_cacheinfo(cpu);
>         struct device_node *np = of_cpu_device_node_get(cpu);
>         struct device_node *prev = NULL;
> -       unsigned int levels = 0, leaves, level;
> +       unsigned int levels = 0, level;
> +       int leaves;
> 
>         if (!of_check_cache_nodes(np)) {
>                 of_node_put(np);
> --
> 2.25.1
> 
> 
> ________________________________
> 本邮件及其附件内容可能含有机密和/或隐私信息,仅供指定个人或机构使用。若您非发件人指定收件人或其代理人,请勿使用、传播、复制或存储此邮件之任何内容或其附件。如您误收本邮件,请即以回复或电话方式通知发件人,并将原始邮件、附件及其所有复本删除。谢谢。
> The contents of this message and any attachments may contain confidential and/or privileged information and are intended exclusively for the addressee(s). If you are not the intended recipient of this message or their agent, please note that any use, dissemination, copying, or storage of this message or its attachments is not allowed. If you receive this message in error, please notify the sender by reply the message or phone and delete this message, any attachments and any copies immediately.
^^^
Gotta sort this out chief, I should probably be deleting this, not
replying to it...

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-06-14 14:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-14 13:35 [PATCH v1] drivers:base:Fix unsigned compared with less than zero Wang Ming
2023-06-14 14:33 ` Conor Dooley [this message]
     [not found]   ` <SG2PR06MB374351CD57614B51FF2E71CABD5BA@SG2PR06MB3743.apcprd06.prod.outlook.com>
     [not found]     ` <20230615-cathedral-concur-969e91b8c792@wendy>
2023-06-16  9:00       ` 回复: " Sudeep Holla

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=20230614-passcode-stimulate-70eecb6d81d2@spud \
    --to=conor@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=machel@vivo.com \
    --cc=opensource.kernel@vivo.com \
    --cc=rafael@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