linux-kernel - Re: [PATCH v3 for-rc 0/2] Fix sge

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 11 Nov 2022 18:22:05 +0200
From:   Leon Romanovsky <leon@...nel.org>
To:     "xuhaoyue (A)" <xuhaoyue1@...ilicon.com>
Cc:     jgg@...dia.com, linux-rdma@...r.kernel.org, linuxarm@...wei.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 for-rc 0/2] Fix sge_num bug

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