From: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Cc: "Iremonger, Bernard" <bernard.iremonger@intel.com>
Subject: Re: [dpdk-dev] [RFC] doc: deprecate legacy code path in ipsec-secgw
Date: Fri, 19 Jul 2019 14:55:50 +0000 [thread overview]
Message-ID: <9F7182E3F746AB4EA17801C148F3C6043366CC08@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <1562835937-24141-1-git-send-email-bernard.iremonger@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Bernard Iremonger
> Sent: Thursday, July 11, 2019 6:06 PM
> To: dev@dpdk.org; Ananyev, Konstantin <konstantin.ananyev@intel.com>;
> akhil.goyal@nxp.com
> Cc: Iremonger, Bernard <bernard.iremonger@intel.com>
> Subject: [dpdk-dev] [RFC] 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.iremonger@intel.com>
> ---
> doc/guides/rel_notes/deprecation.rst | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst
> b/doc/guides/rel_notes/deprecation.rst
> index a7796f4..258fee8 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -82,3 +82,8 @@ Deprecation Notices
> to set new power environment if power environment was already
> initialized.
> In this case the function will return -1 unless the environment is unset first
> (using ``rte_power_unset_env``). Other function usage scenarios will not
> change.
> +
> +* ipsec-secgw: All the ipsec-secgw legacy code path functionality is
> +now
> + available in the librte_ipsec library. It is planned to deprecate the
> +legacy
> + code path in the ipsec-secgw application in the 19.11 release and
> +remove it
> + in the 20.02 release.
> --
> 2.7.4
Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
next prev parent reply other threads:[~2019-07-19 14:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 9:05 Bernard Iremonger
2019-07-19 11:23 ` Ananyev, Konstantin
2019-07-19 14:55 ` Zhang, Roy Fan [this message]
2019-07-24 9:47 ` Akhil Goyal
2019-07-24 10:12 ` [dpdk-dev] [PATCH] " Bernard Iremonger
2019-07-24 10:14 ` Akhil Goyal
2019-07-26 14:06 ` Akhil Goyal
2019-07-26 14:45 ` [dpdk-dev] [EXT] " Anoob Joseph
2019-07-29 8:49 ` Akhil Goyal
2019-07-29 16:33 ` Thomas Monjalon
2019-07-29 20:07 ` Ananyev, Konstantin
2019-07-30 5:55 ` Akhil Goyal
2019-07-30 7:09 ` Thomas Monjalon
2019-07-30 7:20 ` Akhil Goyal
2019-07-30 7:54 ` Thomas Monjalon
2019-07-30 8:48 ` Akhil Goyal
2019-07-30 8:56 ` Thomas Monjalon
2019-07-30 9:03 ` Akhil Goyal
2019-07-30 9:25 ` Ananyev, Konstantin
2019-07-30 11:06 ` Akhil Goyal
2019-07-31 10:19 ` Ananyev, Konstantin
2019-07-31 11:26 ` Akhil Goyal
2019-08-01 7:34 ` Ananyev, Konstantin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9F7182E3F746AB4EA17801C148F3C6043366CC08@IRSMSX101.ger.corp.intel.com \
--to=roy.fan.zhang@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).