netdev - Re: [PATCH ipsec v3 1/1] xfrm: Migrate offload configuration

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] [day] [month] [year] [list]

Message-ID: <Z8qJOVuMr+GamxUO@gauss3.secunet.de>
Date: Fri, 7 Mar 2025 06:50:49 +0100
From: Steffen Klassert <steffen.klassert@...unet.com>
To: Chiachang Wang <chiachangwang@...gle.com>
CC: Leon Romanovsky <leonro@...dia.com>, <netdev@...r.kernel.org>,
	<stanleyjhu@...gle.com>, <yumike@...gle.comy>
Subject: Re: [PATCH ipsec v3 1/1] xfrm: Migrate offload configuration

On Fri, Mar 07, 2025 at 01:42:25PM +0800, Chiachang Wang wrote:
> Hi Leon,
> 
> Thank you for your review and suggestions. I noticed your patches
> haven't been merged into the tree yet. I'm unsure if rebasing my patch
> onto yours would work correctly with the kernel upstream. It seems
> your patches are suitable for merging. Since I'm not familiar with the
> timeline for your patch's inclusion, could you please advise on how
> long it might take for them to be in the tree? This would help me
> rebase my patch properly. or there are any other alternative way
> rather than waiting your patch?

Rebase your patch on top of the ipsec-next tree. This is the target tree
for xfrm changes that will go to -next. Leons patchset is already merged
into this tree.

Thanks!