From: Weihang Li <liweihang@huawei.com>
To: <dledford@redhat.com>, <jgg@nvidia.com>
Cc: <leon@kernel.org>, <linux-rdma@vger.kernel.org>,
<linuxarm@openeuler.org>
Subject: [PATCH for-next 0/6] RDMA/hns: Fix and refactor CMDQ related code
Date: Thu, 4 Feb 2021 14:23:00 +0800 [thread overview]
Message-ID: <1612419786-39173-1-git-send-email-liweihang@huawei.com> (raw)
Remove some dead code in process of CMDQ transmission, and fix an issue
about missing error code.
Lang Cheng (6):
RDMA/hns: Remove unused member and variable of CMDQ
RDMA/hns: Remove unsupported CMDQ mode
RDMA/hns: Fixes missing error code of CMDQ
RDMA/hns: Remove redundant operations on CMDQ
RDMA/hns: Adjust fields and variables about CMDQ tail/head
RDMA/hns: Refactor process of posting CMDQ
drivers/infiniband/hw/hns/hns_roce_common.h | 4 +-
drivers/infiniband/hw/hns/hns_roce_hw_v2.c | 142 ++++++++--------------------
drivers/infiniband/hw/hns/hns_roce_hw_v2.h | 7 --
3 files changed, 42 insertions(+), 111 deletions(-)
--
2.8.1
next reply other threads:[~2021-02-04 6:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 6:23 Weihang Li [this message]
2021-02-04 6:23 ` [PATCH for-next 1/6] RDMA/hns: Remove unused member and variable of CMDQ Weihang Li
2021-02-04 6:23 ` [PATCH for-next 2/6] RDMA/hns: Remove unsupported CMDQ mode Weihang Li
[not found] ` <aabcf1a1-1cdf-5d05-cc11-daa36f9f10fa@huawei.com>
2021-02-07 8:15 ` liweihang
2021-02-07 8:53 ` Leon Romanovsky
2021-02-04 6:23 ` [PATCH for-next 3/6] RDMA/hns: Fixes missing error code of CMDQ Weihang Li
2021-02-04 6:23 ` [PATCH for-next 4/6] RDMA/hns: Remove redundant operations on CMDQ Weihang Li
2021-02-04 6:23 ` [PATCH for-next 5/6] RDMA/hns: Adjust fields and variables about CMDQ tail/head Weihang Li
2021-02-04 6:23 ` [PATCH for-next 6/6] RDMA/hns: Refactor process of posting CMDQ Weihang Li
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=1612419786-39173-1-git-send-email-liweihang@huawei.com \
--to=liweihang@huawei.com \
--cc=dledford@redhat.com \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@openeuler.org \
/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