From: Leon Romanovsky <leon@kernel.org>
To: "xuhaoyue (A)" <xuhaoyue1@hisilicon.com>
Cc: jgg@nvidia.com, 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 18:22:05 +0200 [thread overview]
Message-ID: <Y252rdeqOY2zGosj@unreal> (raw)
In-Reply-To: <48d3efa2-60f8-c0dd-8206-8ca0466f3b77@hisilicon.com>
On Fri, Nov 11, 2022 at 07:41:43PM +0800, xuhaoyue (A) wrote:
> 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?
Up to you and the change you want to send. At this stage, your commit
message must be very descriptive and patch should fix kernel panic and/or
UAPI issue introduced in previous cycle.
> Also, I wonder is that ok to send more than one patch set in the review list.
Yes, you can send, but with two small caveats:
1. You need to try and avoid merge conflicts if series are applied not in
the order of submission.
2. Series should be small.
Bottom line, take a look on RXE patches and DON'T do like them.
Thanks
next prev parent reply other threads:[~2022-11-11 16:22 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)
2022-11-11 16:22 ` Leon Romanovsky [this message]
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=Y252rdeqOY2zGosj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox