From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Mrozowicz, SlawomirX" <slawomirx.mrozowicz@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Mrozowicz, SlawomirX" <slawomirx.mrozowicz@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce public crypto PMD names removal
Date: Mon, 8 May 2017 09:50:19 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D89747818D4C@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <20170504093919.52597-1-slawomirx.mrozowicz@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Slawomir
> Mrozowicz
> Sent: Thursday, May 04, 2017 10:39 AM
> To: Doherty, Declan
> Cc: dev@dpdk.org; Mrozowicz, SlawomirX
> Subject: [dpdk-dev] [PATCH] doc: announce public crypto PMD names
> removal
>
> The following PMD names definitions will be moved to the individual PMDs
> to remove the coupling between crypto PMDs and the librte_cryptodev:
> CRYPTODEV_NAME_NULL_PMD
> CRYPTODEV_NAME_AESNI_MB_PMD
> CRYPTODEV_NAME_AESNI_GCM_PMD
> CRYPTODEV_NAME_OPENSSL_PMD
> CRYPTODEV_NAME_QAT_SYM_PMD
> CRYPTODEV_NAME_SNOW3G_PMD
> CRYPTODEV_NAME_KASUMI_PMD
> CRYPTODEV_NAME_ZUC_PMD
> CRYPTODEV_NAME_ARMV8_PMD
> CRYPTODEV_NAME_SCHEDULER_PMD
> CRYPTODEV_NAME_DPAA2_SEC_PMD
>
> Signed-off-by: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>
Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
next prev parent reply other threads:[~2017-05-08 9:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 9:39 Slawomir Mrozowicz
2017-05-08 9:50 ` De Lara Guarch, Pablo [this message]
2017-05-08 11:02 ` Jerin Jacob
2017-05-08 13:08 ` Trahe, Fiona
2017-05-08 14:59 ` Hemant Agrawal
2017-05-11 0:43 ` Thomas Monjalon
[not found] <1493878976-118626-1-git-send-email-slawomirx.mrozowicz@intel.com>
2017-05-05 15:28 ` Declan Doherty
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=E115CCD9D858EF4F90C690B0DCB4D89747818D4C@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=slawomirx.mrozowicz@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).