From: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
To: "Power, Ciara" <ciara.power@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "gakhil@marvell.com" <gakhil@marvell.com>,
"anoobj@marvell.com" <anoobj@marvell.com>,
"mdr@ashroe.eu" <mdr@ashroe.eu>,
"Doherty, Declan" <declan.doherty@intel.com>
Subject: RE: [PATCH v6 1/5] doc: replace asym crypto code with literal includes
Date: Thu, 10 Feb 2022 16:36:30 +0000 [thread overview]
Message-ID: <MW5PR11MB58095E80C3CC59C43745F15DB82F9@MW5PR11MB5809.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220210155404.3598576-2-ciara.power@intel.com>
> -----Original Message-----
> From: Power, Ciara <ciara.power@intel.com>
> Sent: Thursday, February 10, 2022 3:54 PM
> To: dev@dpdk.org
> Cc: Zhang, Roy Fan <roy.fan.zhang@intel.com>; gakhil@marvell.com;
> anoobj@marvell.com; mdr@ashroe.eu; Power, Ciara
> <ciara.power@intel.com>; Doherty, Declan <declan.doherty@intel.com>
> Subject: [PATCH v6 1/5] doc: replace asym crypto code with literal includes
>
> The programmer's guide for cryptodev included sample code for using
> Asymmetric crypto. This is now replaced with direct code from the test
> application, using literal includes. It is broken into snippets as the
> test application didn't have all of the required code in one function.
>
> Signed-off-by: Ciara Power <ciara.power@intel.com>
> Acked-by: Anoob Joseph <anoobj@marvell.com>
> ---
Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
next prev parent reply other threads:[~2022-02-10 16:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 15:38 [PATCH v4 0/5] crypto: improve asym session usage Ciara Power
2022-02-09 15:38 ` [PATCH v4 1/5] doc: replace asym crypto code with literal includes Ciara Power
2022-02-09 15:38 ` [PATCH v4 2/5] crypto: use single buffer for asymmetric session Ciara Power
2022-02-09 19:52 ` [EXT] " Akhil Goyal
2022-02-09 15:38 ` [PATCH v4 3/5] crypto: hide asym session structure Ciara Power
2022-02-09 15:38 ` [PATCH v4 4/5] crypto: add asym session user data API Ciara Power
2022-02-09 20:09 ` [EXT] " Akhil Goyal
2022-02-09 15:38 ` [PATCH v4 5/5] crypto: modify return value for asym session create Ciara Power
2022-02-09 20:19 ` [EXT] " Akhil Goyal
2022-02-10 14:01 ` [PATCH v5 0/5] crypto: improve asym session usage Ciara Power
2022-02-10 14:01 ` [PATCH v5 1/5] doc: replace asym crypto code with literal includes Ciara Power
2022-02-10 14:01 ` [PATCH v5 2/5] crypto: use single buffer for asymmetric session Ciara Power
2022-02-10 14:34 ` [EXT] " Anoob Joseph
2022-02-10 14:01 ` [PATCH v5 3/5] crypto: hide asym session structure Ciara Power
2022-02-10 14:01 ` [PATCH v5 4/5] crypto: add asym session user data API Ciara Power
2022-02-10 14:01 ` [PATCH v5 5/5] crypto: modify return value for asym session create Ciara Power
2022-02-10 15:53 ` [PATCH v6 0/5] crypto: improve asym session usage Ciara Power
2022-02-10 15:54 ` [PATCH v6 1/5] doc: replace asym crypto code with literal includes Ciara Power
2022-02-10 16:36 ` Zhang, Roy Fan [this message]
2022-02-10 15:54 ` [PATCH v6 2/5] crypto: use single buffer for asymmetric session Ciara Power
2022-02-10 15:54 ` [PATCH v6 3/5] crypto: hide asym session structure Ciara Power
2022-02-10 15:54 ` [PATCH v6 4/5] crypto: add asym session user data API Ciara Power
2022-02-10 15:54 ` [PATCH v6 5/5] crypto: modify return value for asym session create Ciara Power
2022-02-10 22:37 ` [EXT] [PATCH v6 0/5] crypto: improve asym session usage Akhil Goyal
2022-02-11 9:29 ` [PATCH v7 " Ciara Power
2022-02-11 9:29 ` [PATCH v7 1/5] doc: replace asym crypto code with literal includes Ciara Power
2022-02-11 9:29 ` [PATCH v7 2/5] crypto: use single buffer for asymmetric session Ciara Power
2022-02-11 9:29 ` [PATCH v7 3/5] crypto: hide asym session structure Ciara Power
2022-02-11 9:29 ` [PATCH v7 4/5] crypto: add asym session user data API Ciara Power
2022-02-11 9:29 ` [PATCH v7 5/5] crypto: modify return value for asym session create Ciara Power
2022-02-11 14:29 ` [EXT] [PATCH v7 0/5] crypto: improve asym session usage 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=MW5PR11MB58095E80C3CC59C43745F15DB82F9@MW5PR11MB5809.namprd11.prod.outlook.com \
--to=roy.fan.zhang@intel.com \
--cc=anoobj@marvell.com \
--cc=ciara.power@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=mdr@ashroe.eu \
/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).