From: liweihang <liweihang@huawei.com>
To: "jgg@ziepe.ca" <jgg@ziepe.ca>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Linuxarm <linuxarm@huawei.com>
Subject: Re: [PATCH for-next 0/9] RDMA/hns: Various fixes and cleanups
Date: Fri, 22 May 2020 07:39:31 +0000 [thread overview]
Message-ID: <B82435381E3B2943AA4D2826ADEF0B3A0236A7A2@DGGEML522-MBX.china.huawei.com> (raw)
In-Reply-To: 1588931159-56875-1-git-send-email-liweihang@huawei.com
On 2020/5/8 17:46, Weihang Li wrote:
> This series contains the following:
> - #1 ~ #2 are fixes to solve issues found from previous versions.
> - #3 ~ #5 are fixes for recent refactoring codes to 5.8.
> - #6 ~ #9 are various cleanups.
>
> Lang Cheng (2):
> RDMA/hns: Fix cmdq parameter of querying pf timer resource
> RDMA/hns: Store mr len information into mr obj
>
> Lijun Ou (2):
> RDMA/hns: Bugfix for querying qkey
> RDMA/hns: Reserve one sge in order to avoid local length error
>
> Weihang Li (3):
> RDMA/hns: Fix wrong assignment of SRQ's max_wr
> RDMA/hns: Fix error with to_hr_hem_entries_count()
> RDMA/hns: Remove redundant memcpy()
>
> Wenpeng Liang (1):
> RDMA/hns: Fix assignment to ba_pg_sz of eqe
>
> Xi Wang (1):
> RDMA/hns: Rename macro for defining hns hardware page size
>
> drivers/infiniband/hw/hns/hns_roce_alloc.c | 6 ++--
> drivers/infiniband/hw/hns/hns_roce_cq.c | 4 +--
> drivers/infiniband/hw/hns/hns_roce_device.h | 15 +++++---
> drivers/infiniband/hw/hns/hns_roce_hw_v2.c | 53 ++++++++++++-----------------
> drivers/infiniband/hw/hns/hns_roce_hw_v2.h | 4 ++-
> drivers/infiniband/hw/hns/hns_roce_mr.c | 8 +++--
> drivers/infiniband/hw/hns/hns_roce_qp.c | 9 ++---
> drivers/infiniband/hw/hns/hns_roce_srq.c | 10 +++---
> 8 files changed, 56 insertions(+), 53 deletions(-)
>
Hi Jason,
I notice that this series has been marked as "Accepted" on patchwork,
but I can't find them on your for-next branch. Maybe there is something
wrong :)
Thank you
Weihang
next prev parent reply other threads:[~2020-05-22 7:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 9:45 [PATCH for-next 0/9] RDMA/hns: Various fixes and cleanups Weihang Li
2020-05-08 9:45 ` [PATCH for-next 1/9] RDMA/hns: Bugfix for querying qkey Weihang Li
2020-05-08 9:45 ` [PATCH for-next 2/9] RDMA/hns: Fix cmdq parameter of querying pf timer resource Weihang Li
2020-05-08 9:45 ` [PATCH for-next 3/9] RDMA/hns: Fix assignment to ba_pg_sz of eqe Weihang Li
2020-05-08 9:45 ` [PATCH for-next 4/9] RDMA/hns: Fix wrong assignment of SRQ's max_wr Weihang Li
2020-05-08 9:45 ` [PATCH for-next 5/9] RDMA/hns: Fix error with to_hr_hem_entries_count() Weihang Li
2020-05-08 9:45 ` [PATCH for-next 6/9] RDMA/hns: Store mr len information into mr obj Weihang Li
2020-05-08 9:45 ` [PATCH for-next 7/9] RDMA/hns: Remove redundant memcpy() Weihang Li
2020-05-08 9:45 ` [PATCH for-next 8/9] RDMA/hns: Rename macro for defining hns hardware page size Weihang Li
2020-05-08 9:45 ` [PATCH for-next 9/9] RDMA/hns: Reserve one sge in order to avoid local length error Weihang Li
2020-05-22 7:39 ` liweihang [this message]
2020-05-22 9:01 ` [PATCH for-next 0/9] RDMA/hns: Various fixes and cleanups liweihang
2020-05-22 14:28 ` 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=B82435381E3B2943AA4D2826ADEF0B3A0236A7A2@DGGEML522-MBX.china.huawei.com \
--to=liweihang@huawei.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;
as well as URLs for NNTP newsgroup(s).