From: Wenpeng Liang <liangwenpeng@huawei.com>
To: <jgg@nvidia.com>, <leon@kernel.org>
Cc: <linux-rdma@vger.kernel.org>, <linuxarm@huawei.com>,
<liangwenpeng@huawei.com>
Subject: [PATCH for-next 0/5] RDMA/hns: Cleanup for removing redundant statements and judging return values
Date: Sat, 9 Apr 2022 16:32:49 +0800 [thread overview]
Message-ID: <20220409083254.9696-1-liangwenpeng@huawei.com> (raw)
Most static warnings are detected by tools, mainly about:
(1) #1~3: Remove redundant statements.
(2) #4~5: About the return value of the function.
Chengchang Tang (1):
RDMA/hns: Remove unnecessary check for the sgid_attr when modifying QP
Guofeng Yue (1):
RDMA/hns: Remove redundant variable "ret"
Haoyue Xu (1):
RDMA/hns: Init the variable at the suitable place
Wenpeng Liang (1):
RDMA/hns: Add judgment on the execution result of CMDQ that free vf
resource
Yixing Liu (1):
RDMA/hns: Remove unused function to_hns_roce_state()
drivers/infiniband/hw/hns/hns_roce_device.h | 11 --------
drivers/infiniband/hw/hns/hns_roce_hw_v2.c | 29 ++++++++++++---------
drivers/infiniband/hw/hns/hns_roce_qp.c | 20 --------------
3 files changed, 17 insertions(+), 43 deletions(-)
--
2.33.0
next reply other threads:[~2022-04-09 8:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 8:32 Wenpeng Liang [this message]
2022-04-09 8:32 ` [PATCH for-next 1/5] RDMA/hns: Remove unnecessary check for the sgid_attr when modifying QP Wenpeng Liang
2022-04-09 8:32 ` [PATCH for-next 2/5] RDMA/hns: Remove unused function to_hns_roce_state() Wenpeng Liang
2022-04-09 8:32 ` [PATCH for-next 3/5] RDMA/hns: Remove redundant variable "ret" Wenpeng Liang
2022-04-09 8:32 ` [PATCH for-next 4/5] RDMA/hns: Add judgment on the execution result of CMDQ that free vf resource Wenpeng Liang
2022-04-09 8:32 ` [PATCH for-next 5/5] RDMA/hns: Init the variable at the suitable place Wenpeng Liang
2022-04-12 13:42 ` [PATCH for-next 0/5] RDMA/hns: Cleanup for removing redundant statements and judging return values Jason Gunthorpe
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=20220409083254.9696-1-liangwenpeng@huawei.com \
--to=liangwenpeng@huawei.com \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.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