From: Tom Talpey <tom@talpey.com>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
mike.marciniszyn@cornelisnetworks.com
Cc: dennis.dalessandro@cornelisnetworks.com, dledford@redhat.com,
jgg@ziepe.ca, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RDMA/hw/hfi1/tid_rdma: remove unnecessary conversion to bool
Date: Thu, 25 Feb 2021 09:24:23 -0500 [thread overview]
Message-ID: <aeaa298a-8e62-4f0a-c0fe-72cec3c1ed90@talpey.com> (raw)
In-Reply-To: <1614245175-73043-1-git-send-email-jiapeng.chong@linux.alibaba.com>
On 2/25/2021 4:26 AM, Jiapeng Chong wrote:
> Fix the following coccicheck warnings:
>
> ./drivers/infiniband/hw/hfi1/tid_rdma.c:1118:36-41: WARNING: conversion
> to bool not needed here.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
> ---
> drivers/infiniband/hw/hfi1/tid_rdma.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/hw/hfi1/tid_rdma.c b/drivers/infiniband/hw/hfi1/tid_rdma.c
> index 0b1f9e4..8958ea3 100644
> --- a/drivers/infiniband/hw/hfi1/tid_rdma.c
> +++ b/drivers/infiniband/hw/hfi1/tid_rdma.c
> @@ -1115,7 +1115,7 @@ static u32 kern_find_pages(struct tid_rdma_flow *flow,
> }
>
> flow->length = flow->req->seg_len - length;
> - *last = req->isge == ss->num_sge ? false : true;
> + *last = req->isge == !ss->num_sge;
Are you sure this is what you want? The new code seems to compare
an index to a bool (refactoring)
*last = req->isge == (ss->num_sge != 0);
Don't you actually want
*last = req->isge != ss->num_sge;
??
Even then, it seems really hard to read.
> return i;
> }
>
>
prev parent reply other threads:[~2021-02-25 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 9:26 Jiapeng Chong
2021-02-25 14:24 ` Tom Talpey [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=aeaa298a-8e62-4f0a-c0fe-72cec3c1ed90@talpey.com \
--to=tom@talpey.com \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mike.marciniszyn@cornelisnetworks.com \
/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
all inboxes | Powered by JetHome®