public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: "xuhaoyue (A)" <xuhaoyue1@hisilicon.com>
To: Leon Romanovsky <leon@kernel.org>, <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: Fri, 11 Nov 2022 19:41:43 +0800	[thread overview]
Message-ID: <48d3efa2-60f8-c0dd-8206-8ca0466f3b77@hisilicon.com> (raw)
In-Reply-To: <Y2vsZ+qPWJI/R94M@unreal>

Hi Jason and Leon,

Actually, I have another bugfix patch set needed to send, and I am waiting for this patch to apply. That one is not related to this patch set.
Could I send it out, since it is a little late for Linux 6.1?
Also, I wonder is that ok to send more than one patch set in the review list.

Sincerely,
haoyue(Aaron)

On 2022/11/10 2:07:35, Leon Romanovsky wrote:
> 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
>>
> .
> 

  reply	other threads:[~2022-11-11 11:41 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 ` [PATCH v3 for-rc 0/2] Fix sge_num bug Leon Romanovsky
2022-11-11 11:41   ` xuhaoyue (A) [this message]
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=48d3efa2-60f8-c0dd-8206-8ca0466f3b77@hisilicon.com \
    --to=xuhaoyue1@hisilicon.com \
    --cc=jgg@nvidia.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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