From: Akhil Goyal <akhil.goyal@nxp.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"jerinj@marvell.com" <jerinj@marvell.com>,
"Nicolau, Radu" <radu.nicolau@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc/cryptodev: clarify that full xform struct should be zeroed before use
Date: Thu, 20 Jun 2019 14:23:53 +0000 [thread overview]
Message-ID: <VE1PR04MB6639E98A06BFC9DACFD4CC65E6E40@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <348A99DA5F5B7549AA880327E580B43589768C28@IRSMSX101.ger.corp.intel.com>
Hi Fiona,
>
> Hi Akhil, etc,
> Is a deprecation notice necessary for this patch?
> If this patch is accepted I will send a follow-up patchset zeroing the xforms in
> crypto apps.
> Fiona
>
Sorry for late reply.
I don't think this patch need deprecation notice.
> > -----Original Message-----
> > From: Trahe, Fiona
> > Sent: Wednesday, May 15, 2019 5:37 PM
> > To: dev@dpdk.org
> > Cc: Trahe, Fiona <fiona.trahe@intel.com>; akhil.goyal@nxp.com; De Lara
> Guarch, Pablo
> > <pablo.de.lara.guarch@intel.com>; Doherty, Declan
> <declan.doherty@intel.com>; Zhang, Roy Fan
> > <roy.fan.zhang@intel.com>; jerinj@marvell.com; Nicolau, Radu
> <radu.nicolau@intel.com>
> > Subject: [PATCH] doc/cryptodev: clarify that full xform struct should be zeroed
> before use
> >
> > Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
> > ---
> > doc/guides/prog_guide/cryptodev_lib.rst | 10 ++++++++--
> > 1 files changed, 8 insertions(+), 2 deletions(-)
> >
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
next prev parent reply other threads:[~2019-06-20 14:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 16:36 Fiona Trahe
2019-05-15 16:36 ` Fiona Trahe
2019-05-15 16:41 ` Trahe, Fiona
2019-05-15 16:41 ` Trahe, Fiona
2019-06-20 14:23 ` Akhil Goyal [this message]
2019-06-25 12:52 ` Akhil Goyal
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=VE1PR04MB6639E98A06BFC9DACFD4CC65E6E40@VE1PR04MB6639.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=jerinj@marvell.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=radu.nicolau@intel.com \
--cc=roy.fan.zhang@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).