From: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
To: Shen Lichuan <shenlichuan@vivo.com>, jgg@ziepe.ca, leon@kernel.org
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
opensource.kernel@vivo.com
Subject: Re: [PATCH v1] RDMA/sw/rdmavt/mr: Convert to use ERR_CAST()
Date: Wed, 28 Aug 2024 12:06:17 -0400 [thread overview]
Message-ID: <e8cb7488-aea2-4829-9942-dd55b127c25e@cornelisnetworks.com> (raw)
In-Reply-To: <20240828082720.33231-1-shenlichuan@vivo.com>
On 8/28/24 4:27 AM, Shen Lichuan wrote:
> As opposed to open-code, using the ERR_CAST macro clearly indicates that
> this is a pointer to an error value and a type conversion was performed.
>
> Signed-off-by: Shen Lichuan <shenlichuan@vivo.com>
> ---
> drivers/infiniband/sw/rdmavt/mr.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/infiniband/sw/rdmavt/mr.c b/drivers/infiniband/sw/rdmavt/mr.c
> index 7a9afd5231d5..5ed5cfc2b280 100644
> --- a/drivers/infiniband/sw/rdmavt/mr.c
> +++ b/drivers/infiniband/sw/rdmavt/mr.c
> @@ -348,13 +348,13 @@ struct ib_mr *rvt_reg_user_mr(struct ib_pd *pd, u64 start, u64 length,
>
> umem = ib_umem_get(pd->device, start, length, mr_access_flags);
> if (IS_ERR(umem))
> - return (void *)umem;
> + return ERR_CAST(umem);
>
> n = ib_umem_num_pages(umem);
>
> mr = __rvt_alloc_mr(n, pd);
> if (IS_ERR(mr)) {
> - ret = (struct ib_mr *)mr;
> + ret = ERR_CAST(mr);
> goto bail_umem;
> }
>
> @@ -542,7 +542,7 @@ struct ib_mr *rvt_alloc_mr(struct ib_pd *pd, enum ib_mr_type mr_type,
>
> mr = __rvt_alloc_mr(max_num_sg, pd);
> if (IS_ERR(mr))
> - return (struct ib_mr *)mr;
> + return ERR_CAST(mr);
>
> return &mr->ibmr;
> }
I don't think this is really necessary. You are not making the code more
readable. It doesn't simplify things. So I'm not going to Ack it, but I won't
Nak either.
-Denny
next prev parent reply other threads:[~2024-08-28 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 8:27 Shen Lichuan
2024-08-28 16:06 ` Dennis Dalessandro [this message]
2024-08-29 10:17 ` Leon Romanovsky
2024-08-29 10:19 ` Leon Romanovsky
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=e8cb7488-aea2-4829-9942-dd55b127c25e@cornelisnetworks.com \
--to=dennis.dalessandro@cornelisnetworks.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=opensource.kernel@vivo.com \
--cc=shenlichuan@vivo.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®