From: Jason Gunthorpe <jgg@nvidia.com>
To: shao.mingyin@zte.com.cn
Cc: leon@kernel.org, li.haoran7@zte.com.cn,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
viro@zeniv.linux.org.uk, brauner@kernel.org,
agoldberger@nvidia.com, cmeiohas@nvidia.com, msanalla@nvidia.com,
dan.carpenter@linaro.org, mrgolin@amazon.com, phaddad@nvidia.com,
ynachum@amazon.com, mgurtovoy@nvidia.com, yang.yang29@zte.com.cn,
xu.xin16@zte.com.cn, ye.xingchen@zte.com.cn
Subject: Re: [PATCH 0/3] Convert to use ERR_CAST()
Date: Mon, 7 Apr 2025 15:12:52 -0300 [thread overview]
Message-ID: <20250407181252.GA1763135@nvidia.com> (raw)
In-Reply-To: <20250401210730615ULucEmQClX13Q7svZwHsD@zte.com.cn>
On Tue, Apr 01, 2025 at 09:07:30PM +0800, shao.mingyin@zte.com.cn wrote:
> From: Li Haoran <li.haoran7@zte.com.cn>
>
> 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.
>
> Li Haoran (3):
> RDMA/core: Convert to use ERR_CAST()
> RDMA/uverbs: Convert to use ERR_CAST()
> RDMA/core: Convert to use ERR_CAST()
>
> drivers/infiniband/core/mad_rmpp.c | 2 +-
> drivers/infiniband/core/uverbs_cmd.c | 2 +-
> drivers/infiniband/core/verbs.c | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2025-04-07 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 13:07 [PATCH 0/3] Convert to use ERR_CAST() shao.mingyin
2025-04-01 13:08 ` [PATCH 1/3] RDMA/core: " shao.mingyin
2025-04-01 13:09 ` [PATCH 2/3] RDMA/uverbs: " shao.mingyin
2025-04-01 13:10 ` [PATCH 3/3] RDMA/core: " shao.mingyin
2025-04-07 18:12 ` Jason Gunthorpe [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=20250407181252.GA1763135@nvidia.com \
--to=jgg@nvidia.com \
--cc=agoldberger@nvidia.com \
--cc=brauner@kernel.org \
--cc=cmeiohas@nvidia.com \
--cc=dan.carpenter@linaro.org \
--cc=leon@kernel.org \
--cc=li.haoran7@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mgurtovoy@nvidia.com \
--cc=mrgolin@amazon.com \
--cc=msanalla@nvidia.com \
--cc=phaddad@nvidia.com \
--cc=shao.mingyin@zte.com.cn \
--cc=viro@zeniv.linux.org.uk \
--cc=xu.xin16@zte.com.cn \
--cc=yang.yang29@zte.com.cn \
--cc=ye.xingchen@zte.com.cn \
--cc=ynachum@amazon.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;
as well as URLs for NNTP newsgroup(s).