> -----Original Message-----
> From: Thomas Monjalon [mailto:[email protected]]
> Sent: Monday, July 29, 2019 5:34 PM
> To: Iremonger, Bernard <[email protected]>
> Cc: [email protected]; Akhil Goyal <[email protected]>; Anoob Joseph
> <[email protected]>; Ananyev, Konstantin
> <[email protected]>; Jerin Jacob Kollanukkaran
> <[email protected]>; Narayana Prasad Raju Athreya
> <[email protected]>
> Subject: Re: [dpdk-dev] [EXT] [PATCH] doc: deprecate legacy code path in
> ipsec-secgw
>
> > > > All the functionality of the legacy code path in now available in the
> > > > librte_ipsec
> > > > library. It is planned to deprecate the legacy code path in the 19.11
> > > > release and
> > > > remove the legacy code path in the 20.02 release.
> > > >
> > > > Signed-off-by: Bernard Iremonger <[email protected]>
> > > > Acked-by: Konstantin Ananyev <[email protected]>
> > > > Acked-by: Fan Zhang <[email protected]>
> > > > Acked-by: Akhil Goyal <[email protected]>
> > > > ---
> > > > doc/guides/rel_notes/deprecation.rst | 5 +++++
> > > > 1 file changed, 5 insertions(+)
> > > >
> > > Acked-by: Anoob Joseph <[email protected]>
> >
> > Applied to dpdk-next-crypto
>
> Why do we have a deprecation notice for some code path in an example?
> The deprecation notices are for the API.
>
> I think you can drop the legacy code in 19.11,
> and I don't merge this patch in master.
Ok, if we don't need a formal deprecation note for that - even better.
Thanks
Konstantin
