From: Jason Gunthorpe <jgg@nvidia.com>
To: cgel.zte@gmail.com
Cc: chi.minghao@zte.com.cn, dennis.dalessandro@cornelisnetworks.com,
devesh.s.sharma@oracle.com, dledford@redhat.com, leon@kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
mbloch@nvidia.com, selvin.xavier@broadcom.com, trix@redhat.com,
zealci@zte.com.cn
Subject: Re: [PATCH for-next v5] RDMA/ocrdma: remove unneeded variable
Date: Wed, 5 Jan 2022 13:54:11 -0400 [thread overview]
Message-ID: <20220105175411.GA2844588@nvidia.com> (raw)
In-Reply-To: <20211215055421.441375-1-chi.minghao@zte.com.cn>
On Wed, Dec 15, 2021 at 05:54:21AM +0000, cgel.zte@gmail.com wrote:
> From: Minghao Chi <chi.minghao@zte.com.cn>
>
> Return status directly from function called.
>
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: Minghao Chi <chi.minghao@zte.com.cn>
> ---
> drivers/infiniband/hw/ocrdma/ocrdma_verbs.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2022-01-05 17:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 1:52 [PATCH] drivers:ocrdma:remove unneeded variable cgel.zte
2021-12-09 13:08 ` Tom Rix
2021-12-10 1:32 ` [PATCHv2] " cgel.zte
2021-12-14 6:45 ` Devesh Sharma
2021-12-14 8:10 ` [PATCH v3 ocrdma-next] drivers: ocrdma: remove " cgel.zte
2021-12-14 8:43 ` [External] : " Devesh Sharma
2021-12-14 9:23 ` [PATCH for-next v4] RDMA/ocrdma: " cgel.zte
2021-12-14 11:12 ` [External] : " Devesh Sharma
2021-12-14 23:50 ` Jason Gunthorpe
2021-12-15 5:54 ` [PATCH for-next v5] " cgel.zte
2022-01-03 7:58 ` Leon Romanovsky
2022-01-05 17:54 ` 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=20220105175411.GA2844588@nvidia.com \
--to=jgg@nvidia.com \
--cc=cgel.zte@gmail.com \
--cc=chi.minghao@zte.com.cn \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=devesh.s.sharma@oracle.com \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=selvin.xavier@broadcom.com \
--cc=trix@redhat.com \
--cc=zealci@zte.com.cn \
/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).