From: Weihang Li <liweihang@hisilicon.com>
To: <dledford@redhat.com>, <jgg@ziepe.ca>
Cc: <linux-rdma@vger.kernel.org>, <linuxarm@huawei.com>
Subject: [PATCH v2 for-next 0/9] RDMA/hns: Cleanups for hip08
Date: Tue, 5 Nov 2019 19:07:53 +0800 [thread overview]
Message-ID: <1572952082-6681-1-git-send-email-liweihang@hisilicon.com> (raw)
These series just make cleanups without changing code logic.
[patch 1/9 ~ 3/9] remove unused variables and structures.
[patch 4/9 ~ 5/9] modify field and function names.
[patch 6/9 ~ 7/9] remove dead codes to simplify functions.
[patch 8/9] replaces non-standard return value with linux error codes.
[patch 9/9] does some fixes on printings.
Changelog
v1->v2: Remove "{topost}" in titles.
Lang Cheng (3):
RDMA/hns: Remove unnecessary structure hns_roce_sqp
RDMA/hns: Simplify doorbell initialization code
RDMA/hns: Modify hns_roce_hw_v2_get_cfg to simplify the code
Wenpeng Liang (1):
RDMA/hns: Modify appropriate printings
Yixian Liu (4):
RDMA/hns: Delete unnecessary variable max_post
RDMA/hns: Delete unnecessary uar from hns_roce_cq
RDMA/hns: Modify fields of struct hns_roce_srq
RDMA/hns: Fix non-standard error codes
Yixing Liu (1):
RDMA/hns: Replace not intuitive function/macro names
drivers/infiniband/hw/hns/hns_roce_alloc.c | 4 +-
drivers/infiniband/hw/hns/hns_roce_cmd.h | 14 +++----
drivers/infiniband/hw/hns/hns_roce_cq.c | 51 +++++++++++-----------
drivers/infiniband/hw/hns/hns_roce_device.h | 22 +++-------
drivers/infiniband/hw/hns/hns_roce_hw_v1.c | 12 +++---
drivers/infiniband/hw/hns/hns_roce_hw_v2.c | 37 ++++++----------
drivers/infiniband/hw/hns/hns_roce_main.c | 4 +-
drivers/infiniband/hw/hns/hns_roce_mr.c | 65 +++++++++++++++--------------
drivers/infiniband/hw/hns/hns_roce_pd.c | 2 +-
drivers/infiniband/hw/hns/hns_roce_qp.c | 18 ++++----
drivers/infiniband/hw/hns/hns_roce_srq.c | 58 ++++++++++++-------------
11 files changed, 132 insertions(+), 155 deletions(-)
--
2.8.1
next reply other threads:[~2019-11-05 11:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 11:07 Weihang Li [this message]
2019-11-05 11:07 ` [PATCH v2 for-next 1/9] RDMA/hns: Delete unnecessary variable max_post Weihang Li
2019-11-05 11:07 ` [PATCH v2 for-next 2/9] RDMA/hns: Remove unnecessary structure hns_roce_sqp Weihang Li
2019-11-05 11:07 ` [PATCH v2 for-next 3/9] RDMA/hns: Delete unnecessary uar from hns_roce_cq Weihang Li
2019-11-05 11:07 ` [PATCH v2 for-next 4/9] RDMA/hns: Modify fields of struct hns_roce_srq Weihang Li
2019-11-05 11:07 ` [PATCH v2 for-next 5/9] RDMA/hns: Replace not intuitive function/macro names Weihang Li
2019-11-05 11:07 ` [PATCH v2 for-next 6/9] RDMA/hns: Simplify doorbell initialization code Weihang Li
2019-11-05 11:08 ` [PATCH v2 for-next 7/9] RDMA/hns: Modify hns_roce_hw_v2_get_cfg to simplify the code Weihang Li
2019-11-05 11:08 ` [PATCH v2 for-next 8/9] RDMA/hns: Fix non-standard error codes Weihang Li
2019-11-05 17:00 ` Leon Romanovsky
2019-11-06 10:44 ` Weihang Li
2019-11-06 15:43 ` Leon Romanovsky
2019-11-08 8:11 ` Weihang Li
2019-11-05 11:08 ` [PATCH v2 for-next 9/9] RDMA/hns: Modify appropriate printings Weihang Li
2019-11-08 20:45 ` [PATCH v2 for-next 0/9] RDMA/hns: Cleanups for hip08 Jason Gunthorpe
2019-11-09 2:18 ` 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=1572952082-6681-1-git-send-email-liweihang@hisilicon.com \
--to=liweihang@hisilicon.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--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