From: Akhil Goyal <gakhil@marvell.com>
To: "Power, Ciara" <ciara.power@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"g.singh@nxp.com" <g.singh@nxp.com>,
"konstantin.v.ananyev@yandex.ru" <konstantin.v.ananyev@yandex.ru>,
"Nicolau, Radu" <radu.nicolau@intel.com>,
"ruifeng.wang@arm.com" <ruifeng.wang@arm.com>,
"matan@nvidia.com" <matan@nvidia.com>,
"fanzhang.oss@gmail.com" <fanzhang.oss@gmail.com>
Subject: RE: [PATCH] doc: announce deprecation for security ops
Date: Thu, 6 Jul 2023 18:32:54 +0000 [thread overview]
Message-ID: <CO6PR18MB4484582CC3F6CCBD8FFB2EB0D82CA@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <SN7PR11MB7639F9B4FA811573A8A4C94FE62CA@SN7PR11MB7639.namprd11.prod.outlook.com>
> > Subject: [PATCH] doc: announce deprecation for security ops
> >
> > Structure rte_security_ops and rte_security_ctx are meant to be used by
> > rte_security library and the PMDs associated.
> > These will be moved to an internal header in DPDK 23.11 release.
> >
> > Signed-off-by: Akhil Goyal <gakhil@marvell.com>
> > ---
> <snip>
>
> Seems a reasonable change to me.
>
> Acked-by: Ciara Power <ciara.power@intel.com>
Applied to dpdk-next-crypto
prev parent reply other threads:[~2023-07-06 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 19:44 Akhil Goyal
2023-07-05 10:59 ` Hemant Agrawal
2023-07-05 11:31 ` Konstantin Ananyev
2023-07-05 14:06 ` Jerin Jacob
2023-07-06 10:53 ` Power, Ciara
2023-07-06 18:32 ` Akhil Goyal [this message]
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=CO6PR18MB4484582CC3F6CCBD8FFB2EB0D82CA@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=anoobj@marvell.com \
--cc=ciara.power@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=g.singh@nxp.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=matan@nvidia.com \
--cc=ndabilpuram@marvell.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=radu.nicolau@intel.com \
--cc=ruifeng.wang@arm.com \
--cc=thomas@monjalon.net \
/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).