From: Weihang Li <liweihang@hisilicon.com>
To: <dledford@redhat.com>, <jgg@ziepe.ca>
Cc: <linux-rdma@vger.kernel.org>, <linuxarm@huawei.com>
Subject: [PATCH for-next 0/4] RDMA/hns: Refactor codes of CQ
Date: Mon, 18 Nov 2019 10:34:49 +0800 [thread overview]
Message-ID: <1574044493-46984-1-git-send-email-liweihang@hisilicon.com> (raw)
This series redefine/rename/remove some interfaces to improve readability
and maintainability of codes of CQ in hip08.
The 4th patch has conflict with "RDMA/hns: Add support for reporting wc
as software mode", will send a rebased one if any of them was applied.
Yixian Liu (4):
RDMA/hns: Redefine interfaces used in creating cq
RDMA/hns: Redefine the member of hns_roce_cq struct
RDMA/hns: Rename the functions used inside creating cq
RDMA/hns: Delete unnecessary callback functions for cq
drivers/infiniband/hw/hns/hns_roce_cmd.h | 4 +-
drivers/infiniband/hw/hns/hns_roce_cq.c | 271 +++++++++++-----------------
drivers/infiniband/hw/hns/hns_roce_device.h | 27 +--
drivers/infiniband/hw/hns/hns_roce_hw_v1.c | 26 ++-
drivers/infiniband/hw/hns/hns_roce_hw_v2.c | 13 +-
drivers/infiniband/hw/hns/hns_roce_main.c | 4 +-
6 files changed, 141 insertions(+), 204 deletions(-)
--
2.8.1
next reply other threads:[~2019-11-18 2:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 2:34 Weihang Li [this message]
2019-11-18 2:34 ` [PATCH for-next 1/4] RDMA/hns: Redefine interfaces used in creating cq Weihang Li
2019-11-18 2:34 ` [PATCH for-next 2/4] RDMA/hns: Redefine the member of hns_roce_cq struct Weihang Li
2019-11-18 2:34 ` [PATCH for-next 3/4] RDMA/hns: Rename the functions used inside creating cq Weihang Li
2019-11-18 2:34 ` [PATCH for-next 4/4] RDMA/hns: Delete unnecessary callback functions for cq Weihang Li
2019-11-22 20:48 ` [PATCH for-next 0/4] RDMA/hns: Refactor codes of CQ 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=1574044493-46984-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.