From: Leon Romanovsky <leon@kernel.org>
To: Wenpeng Liang <liangwenpeng@huawei.com>
Cc: jgg@nvidia.com, linux-rdma@vger.kernel.org, linuxarm@huawei.com
Subject: Re: [PATCH for-next 0/4] RDMA/hns: Bugfixes or cleanups for resource specs or numbers
Date: Tue, 30 Aug 2022 10:27:01 +0300 [thread overview]
Message-ID: <Yw27xaDjcg5iAonk@unreal> (raw)
In-Reply-To: <20220829105021.1427804-1-liangwenpeng@huawei.com>
On Mon, Aug 29, 2022 at 06:50:17PM +0800, Wenpeng Liang wrote:
> The following is the outline of each patch:
> (1)#1~#3: The earliest code sets the resource specification incorrectly.
> (2)#4: The earliest code used this parameter, but the latest code no longer
> needs it.
>
> Chengchang Tang (1):
> RDMA/hns: Fix supported page size
>
> Wenpeng Liang (2):
> RDMA/hns: Fix wrong fixed value of qp->rq.wqe_shift
> RDMA/hns: Remove redundant member doorbell_qpn of struct hns_roce_qp
I took these to rdma-rc.
>
> Yixing Liu (1):
> RDMA/hns: Remove the num_qpc_timer variable
And this to rdma-next.
>
> drivers/infiniband/hw/hns/hns_roce_device.h | 2 --
> drivers/infiniband/hw/hns/hns_roce_hw_v2.c | 5 ++---
> drivers/infiniband/hw/hns/hns_roce_hw_v2.h | 4 ++--
> drivers/infiniband/hw/hns/hns_roce_main.c | 2 +-
> drivers/infiniband/hw/hns/hns_roce_qp.c | 10 ++--------
> 5 files changed, 7 insertions(+), 16 deletions(-)
>
> --
> 2.30.0
>
prev parent reply other threads:[~2022-08-30 7:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 10:50 [PATCH for-next 0/4] RDMA/hns: Bugfixes or cleanups for resource specs or numbers Wenpeng Liang
2022-08-29 10:50 ` [PATCH for-next 1/4] RDMA/hns: Fix supported page size Wenpeng Liang
2022-08-29 10:50 ` [PATCH for-next 2/4] RDMA/hns: Fix wrong fixed value of qp->rq.wqe_shift Wenpeng Liang
2022-08-29 10:50 ` [PATCH for-next 3/4] RDMA/hns: Remove the num_qpc_timer variable Wenpeng Liang
2022-08-29 10:50 ` [PATCH for-next 4/4] RDMA/hns: Remove redundant member doorbell_qpn of struct hns_roce_qp Wenpeng Liang
2022-08-30 7:27 ` Leon Romanovsky [this message]
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=Yw27xaDjcg5iAonk@unreal \
--to=leon@kernel.org \
--cc=jgg@nvidia.com \
--cc=liangwenpeng@huawei.com \
--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