[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YwNCd2zp6lstaeQf@unreal>
Date: Mon, 22 Aug 2022 11:46:47 +0300
From: Leon Romanovsky <leon@...nel.org>
To: Steffen Klassert <steffen.klassert@...unet.com>
Cc: "David S . Miller" <davem@...emloft.net>,
Herbert Xu <herbert@...dor.apana.org.au>,
netdev@...r.kernel.org, Raed Salem <raeds@...dia.com>,
ipsec-devel <devel@...ux-ipsec.org>
Subject: Re: [PATCH xfrm-next v2 2/6] xfrm: allow state full offload mode
On Mon, Aug 22, 2022 at 10:01:08AM +0200, Steffen Klassert wrote:
> On Thu, Aug 18, 2022 at 04:28:12PM +0300, Leon Romanovsky wrote:
> > On Thu, Aug 18, 2022 at 12:12:20PM +0200, Steffen Klassert wrote:
> > > On Tue, Aug 16, 2022 at 11:59:23AM +0300, Leon Romanovsky wrote:
> > > > From: Leon Romanovsky <leonro@...dia.com>
> > > >
> > > > Allow users to configure xfrm states with full offload mode.
> > > > The full mode must be requested both for policy and state, and
> > > > such requires us to do not implement fallback.
> > > >
> > > > We explicitly return an error if requested full mode can't
> > > > be configured.
> > > >
> > > > Reviewed-by: Raed Salem <raeds@...dia.com>
> > > > Signed-off-by: Leon Romanovsky <leonro@...dia.com>
> > >
> > > This one needs to be ACKed by the driver maintainers.
> >
> > Why? Only crypto is supported in upstream kernel.
>
> Because it touches code hat is under their maintainance.
> They should at least be CCed on this patch.
No problem, will do.
Thanks
Powered by blists - more mailing lists