From: Jason Gunthorpe <jgg@nvidia.com>
To: Haoyue Xu <xuhaoyue1@hisilicon.com>
Cc: leon@kernel.org, linux-rdma@vger.kernel.org, linuxarm@huawei.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH for-next 0/6] Bugfix for GID and PBL page
Date: Wed, 7 Dec 2022 19:53:32 -0400 [thread overview]
Message-ID: <Y5EnfM+Lkwo9EXS7@nvidia.com> (raw)
In-Reply-To: <20221126102911.2921820-1-xuhaoyue1@hisilicon.com>
On Sat, Nov 26, 2022 at 06:29:05PM +0800, Haoyue Xu wrote:
> This patch set mainly fixes the GID problem caused by free mr.
> The second and third patches fix the error on the PBL.
> The last three patches fix minor errors found while running
> the rdma-core tests.
>
> 1.#1: The GID problem caused by free mr
> 2.#2-#3: Fix the error on the PBL
> 3.#4-#5: Two minor return errors
> 4.#6: The default caps error
>
> Chengchang Tang (5):
> RDMA/hns: Fix AH attr queried by query_qp
> RDMA/hns: Fix PBL page MTR find
> RDMA/hns: Fix page size cap from firmwall
> RDMA/hns: Fix error code of CMD
> RDMA/hns: Fix XRC caps on HIP08
>
> Yixing Liu (1):
> RDMA/hns: Fix the gid problem caused by free mr
Applied to for-next
Thanks,
Jason
prev parent reply other threads:[~2022-12-07 23:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 10:29 [PATCH for-next 0/6] Bugfix for GID and PBL page Haoyue Xu
2022-11-26 10:29 ` [PATCH for-next 1/6] RDMA/hns: Fix the gid problem caused by free mr Haoyue Xu
2022-11-26 10:29 ` [PATCH for-next 2/6] RDMA/hns: Fix AH attr queried by query_qp Haoyue Xu
2022-11-26 10:29 ` [PATCH for-next 3/6] RDMA/hns: Fix PBL page MTR find Haoyue Xu
2022-11-26 10:29 ` [PATCH for-next 4/6] RDMA/hns: Fix page size cap from firmwall Haoyue Xu
2022-11-26 10:29 ` [PATCH for-next 5/6] RDMA/hns: Fix error code of CMD Haoyue Xu
2022-11-26 10:29 ` [PATCH for-next 6/6] RDMA/hns: Fix XRC caps on HIP08 Haoyue Xu
2022-12-07 23:53 ` Jason Gunthorpe [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=Y5EnfM+Lkwo9EXS7@nvidia.com \
--to=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=xuhaoyue1@hisilicon.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.