netdev - Re: [PATCH xfrm-next v9 0/8] Extend XFRM core to allow packet 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20221202115213.0055aa4a@kernel.org>
Date:   Fri, 2 Dec 2022 11:52:13 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Leon Romanovsky <leon@...nel.org>
Cc:     Steffen Klassert <steffen.klassert@...unet.com>,
        "David S. Miller" <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Herbert Xu <herbert@...dor.apana.org.au>,
        netdev@...r.kernel.org, Bharat Bhushan <bbhushan2@...vell.com>
Subject: Re: [PATCH xfrm-next v9 0/8] Extend XFRM core to allow packet
 offload configuration

On Fri, 2 Dec 2022 21:45:47 +0200 Leon Romanovsky wrote:
> > More of a question of whether we can reasonably expect to merge all 
> > the driver code in a single release cycle. If not then piecemeal
> > merging is indeed inevitable. But if Steffen is happy with the core
> > changes whether they are in tree for 6.2 or not should not matter.
> > An upstream user can't access them anyway, it'd only matter to an
> > out-of-tree consumer.
> > 
> > That's just my 2 cents, whatever Steffen prefers matters most.  
> 
> There are no out-of-tree users, just ton of mlx5 refactoring to natively
> support packet offload.

30 patches is just two series, that's mergeable in a week.
You know, if it builds cleanly.. :S  Dunno.