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]
Message-ID: <20221117122043.GM704954@gauss3.secunet.de>
Date:   Thu, 17 Nov 2022 13:20:43 +0100
From:   Steffen Klassert <steffen.klassert@...unet.com>
To:     Saeed Mahameed <saeed@...nel.org>
CC:     Leon Romanovsky <leon@...nel.org>,
        "David S. Miller" <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Herbert Xu <herbert@...dor.apana.org.au>,
        Jakub Kicinski <kuba@...nel.org>, <netdev@...r.kernel.org>
Subject: Re: [PATCH xfrm-next v7 0/8] Extend XFRM core to allow packet
 offload configuration

On Wed, Nov 16, 2022 at 03:07:13PM -0800, Saeed Mahameed wrote:
> On 15 Nov 21:00, Leon Romanovsky wrote:
> > On Tue, Nov 15, 2022 at 07:30:20PM +0100, Steffen Klassert wrote:
> > > On Tue, Nov 15, 2022 at 08:09:48PM +0200, Leon Romanovsky wrote:
> > > > On Wed, Nov 09, 2022 at 02:54:28PM +0200, Leon Romanovsky wrote:
> > > > > From: Leon Romanovsky <leonro@...dia.com>
> > > > >
> > > > > Changelog:
> > > > > v7: As was discussed in IPsec workshop:
> > > >
> > > > Steffen, can we please merge the series so we won't miss another kernel
> > > > release?
> > > 
> > > I'm already reviewing the patchset. But as I said at the
> > > IPsec workshop, there is no guarantee that it will make
> > > it during this release cycle.
> > 
> 
> BTW mlx5 patches are almost ready and fully reviewed, will be ready by
> early next week.
> 
> Steffen in case you will be ready, how do you want to receive the whole
> package? I guess we will need to post all the patches for a final time,
> including mlx5 driver.

I guess you want me to take both, the xfrm and mlx5 patches, right?
I'm ok with that if nobody else objects to it.

Please split it anyways into a xfrm and a mlx5 pachset. I'll
merge both separate once we are ready.


Thanks!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ