Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 11 Nov 2022 18:22:05 +0200
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
Message-ID: <Y252rdeqOY2zGosj@unreal>
References: <20221108133847.2304539-1-xuhaoyue1@hisilicon.com>
 <Y2vsZ+qPWJI/R94M@unreal>
 <48d3efa2-60f8-c0dd-8206-8ca0466f3b77@hisilicon.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <48d3efa2-60f8-c0dd-8206-8ca0466f3b77@hisilicon.com>
Precedence: bulk

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