From: "Power, Ciara" <ciara.power@intel.com>
To: "Coyle, David" <david.coyle@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Ji, Kai" <kai.ji@intel.com>,
"anoobj@marvell.com" <anoobj@marvell.com>,
"O'Sullivan, Kevin" <kevin.osullivan@intel.com>,
"Coyle, David" <david.coyle@intel.com>,
"probb@iol.unh.edu" <probb@iol.unh.edu>
Subject: RE: [PATCH v3 0/2] crypto/scheduler: add support for DOCSIS security protocol
Date: Fri, 15 Sep 2023 10:18:47 +0000 [thread overview]
Message-ID: <SN7PR11MB7639EBA20DAC0B1336F78E99E6F6A@SN7PR11MB7639.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230914152207.19794-1-david.coyle@intel.com>
> -----Original Message-----
> From: David Coyle <david.coyle@intel.com>
> Sent: Thursday, September 14, 2023 4:22 PM
> To: dev@dpdk.org
> Cc: Ji, Kai <kai.ji@intel.com>; anoobj@marvell.com; O'Sullivan, Kevin
> <kevin.osullivan@intel.com>; Coyle, David <david.coyle@intel.com>
> Subject: [PATCH v3 0/2] crypto/scheduler: add support for DOCSIS security
> protocol
>
> This patchset adds support to the cryptodev scheduler PMD and unit
> tests for the DOCSIS security protocol. Support for other stateless
> security protocols can be added in the future as required with relative
> ease now that the framework is in place.
>
Recheck-request: iol-sample-apps-testing
FIPS warning, could be just the NIST ACVP API known issue, trying retest.
next prev parent reply other threads:[~2023-09-15 10:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 10:14 [PATCH 0/2] crypto/scheduler: add support for security protocols David Coyle
2023-08-09 10:14 ` [PATCH 1/2] crypto/scheduler: support " David Coyle
2023-08-09 10:14 ` [PATCH 2/2] test/crypto: add security tests for cryptodev scheduler David Coyle
2023-08-11 10:23 ` [PATCH v2 0/2] crypto/scheduler: add support for security protocols David Coyle
2023-08-11 10:24 ` [PATCH v2 1/2] crypto/scheduler: support " David Coyle
2023-08-11 10:24 ` [PATCH v2 2/2] test/crypto: add security tests for cryptodev scheduler David Coyle
2023-08-11 11:09 ` [EXT] [PATCH v2 0/2] crypto/scheduler: add support for security protocols Anoob Joseph
2023-09-11 16:02 ` Coyle, David
2023-09-13 7:02 ` Anoob Joseph
2023-09-14 15:22 ` [PATCH v3 0/2] crypto/scheduler: add support for DOCSIS security protocol David Coyle
2023-09-14 15:22 ` [PATCH v3 1/2] crypto/scheduler: support " David Coyle
2023-09-18 11:02 ` [EXT] " Anoob Joseph
2023-09-19 14:16 ` Coyle, David
2023-09-14 15:22 ` [PATCH v3 2/2] test/crypto: add DOCSIS security tests for cryptodev scheduler David Coyle
2023-09-15 10:18 ` Power, Ciara [this message]
2023-09-15 14:02 ` [PATCH v3 0/2] crypto/scheduler: add support for DOCSIS security protocol Power, Ciara
2023-09-19 14:14 ` [PATCH v4 " David Coyle
2023-09-19 14:14 ` [PATCH v4 1/2] crypto/scheduler: support " David Coyle
2023-09-19 14:14 ` [PATCH v4 2/2] test/crypto: add DOCSIS security tests for cryptodev scheduler David Coyle
2023-09-20 5:45 ` [EXT] [PATCH v4 0/2] crypto/scheduler: add support for DOCSIS security protocol Anoob Joseph
2023-09-21 7:18 ` 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=SN7PR11MB7639EBA20DAC0B1336F78E99E6F6A@SN7PR11MB7639.namprd11.prod.outlook.com \
--to=ciara.power@intel.com \
--cc=anoobj@marvell.com \
--cc=david.coyle@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=kevin.osullivan@intel.com \
--cc=probb@iol.unh.edu \
/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).