> -----Original Message-----
> From: Thomas Monjalon [mailto:tho...@monjalon.net]
> Sent: Monday, July 29, 2019 5:34 PM
> To: Iremonger, Bernard <bernard.iremon...@intel.com>
> Cc: dev@dpdk.org; Akhil Goyal <akhil.go...@nxp.com>; Anoob Joseph
> <ano...@marvell.com>; Ananyev, Konstantin
> <konstantin.anan...@intel.com>; Jerin Jacob Kollanukkaran
> <jer...@marvell.com>; Narayana Prasad Raju Athreya
> <pathr...@marvell.com>
> 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 <bernard.iremon...@intel.com>
> > > > Acked-by: Konstantin Ananyev <konstantin.anan...@intel.com>
> > > > Acked-by: Fan Zhang <roy.fan.zh...@intel.com>
> > > > Acked-by: Akhil Goyal <akhil.go...@nxp.com>
> > > > ---
> > > > doc/guides/rel_notes/deprecation.rst | 5 +++++
> > > > 1 file changed, 5 insertions(+)
> > > >
> > > Acked-by: Anoob Joseph <ano...@marvell.com>
> >
> > 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
