From: Leon Romanovsky <leon@kernel.org>
To: Haoyue Xu <xuhaoyue1@hisilicon.com>, jgg@nvidia.com
Cc: linux-rdma@vger.kernel.org, linuxarm@huawei.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 for-rc 0/2] Fix sge_num bug
Date: Wed, 9 Nov 2022 20:07:35 +0200 [thread overview]
Message-ID: <Y2vsZ+qPWJI/R94M@unreal> (raw)
In-Reply-To: <20221108133847.2304539-1-xuhaoyue1@hisilicon.com>
On Tue, Nov 08, 2022 at 09:38:45PM +0800, Haoyue Xu wrote:
> The patchset mainly fixes the sge_num bug relates to sq_inline.
>
> Changes since v2:
> 1. Move the refactor rq_inline and new CQE inline patches to go
> into for-next after this bugfix apply.
> 2. Change the commit message to better explain the bug.
> V2 Link: https://patchwork.kernel.org/project/linux-rdma/cover/20221026095054.2384620-1-xuhaoyue1@hisilicon.com/
>
> Luoyouming (2):
> RDMA/hns: Fix ext_sge num error when post send
> RDMA/hns: Fix the problem of sge nums
>
> drivers/infiniband/hw/hns/hns_roce_device.h | 3 +
> drivers/infiniband/hw/hns/hns_roce_hw_v2.c | 3 +-
> drivers/infiniband/hw/hns/hns_roce_main.c | 18 +++-
> drivers/infiniband/hw/hns/hns_roce_qp.c | 107 ++++++++++++++++----
> include/uapi/rdma/hns-abi.h | 15 +++
Jason,
I think that it was you who asked to send it to -rc. Given the amount of
changes together with UAPI in second patch, are you sure that it is -rc4
material?
Thanks
> 5 files changed, 125 insertions(+), 21 deletions(-)
>
> --
> 2.30.0
>
next prev parent reply other threads:[~2022-11-09 18:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 13:38 [PATCH v3 for-rc 0/2] Fix sge_num bug Haoyue Xu
2022-11-08 13:38 ` [PATCH v3 for-rc 1/2] RDMA/hns: Fix ext_sge num error when post send Haoyue Xu
2022-11-08 13:38 ` [PATCH v3 for-rc 2/2] RDMA/hns: Fix the problem of sge nums Haoyue Xu
2022-11-09 18:07 ` Leon Romanovsky [this message]
2022-11-11 11:41 ` [PATCH v3 for-rc 0/2] Fix sge_num bug xuhaoyue (A)
2022-11-11 16:22 ` Leon Romanovsky
2022-11-19 0:23 ` Jason Gunthorpe
2022-11-30 8:59 ` xuhaoyue (A)
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=Y2vsZ+qPWJI/R94M@unreal \
--to=leon@kernel.org \
--cc=jgg@nvidia.com \
--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.