From: Akhil Goyal <akhil.goyal@nxp.com>
To: Fan Zhang <roy.fan.zhang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Damian Nowak <damianx.nowak@intel.com>,
Lukasz Krakowiak <lukaszx.krakowiak@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] crypto/aesni_mb: add plain sha support
Date: Tue, 18 Dec 2018 10:30:43 +0000 [thread overview]
Message-ID: <34349130-5efe-0c71-75da-6ea3e6ed1a94@nxp.com> (raw)
In-Reply-To: <20181213151817.27478-1-roy.fan.zhang@intel.com>
On 12/13/2018 8:48 PM, Fan Zhang wrote:
> From: Damian Nowak <damianx.nowak@intel.com>
>
> This patch adds the plain SHAx algorithm support to AESNI-MB PMD.
>
> This patch depends on the following patch:
> "crypto/aesni_mb: use architure independent marcos"
> (http://patchwork.dpdk.org/patch/48633/").
>
> Signed-off-by: Damian Nowak <damianx.nowak@intel.com>
> Signed-off-by: Lukasz Krakowiak <lukaszx.krakowiak@intel.com>
> Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
> ---
>
Applied to dpdk-next-crypto
Thanks
next prev parent reply other threads:[~2018-12-18 10:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 17:24 [dpdk-dev] [PATCH] crypto/aesni_mb: add SHA support Fan Zhang
2018-12-13 15:18 ` [dpdk-dev] [PATCH v2] crypto/aesni_mb: add plain sha support Fan Zhang
2018-12-18 10:30 ` Akhil Goyal [this message]
2018-12-19 23:24 ` [dpdk-dev] [PATCH v3 0/3] " Fan Zhang
2018-12-19 23:24 ` [dpdk-dev] [PATCH v3 1/3] " Fan Zhang
2018-12-19 23:24 ` [dpdk-dev] [PATCH v3 2/3] test: add aesni-mb sha test Fan Zhang
2018-12-19 23:24 ` [dpdk-dev] [PATCH v3 3/3] doc: update release note and PMD information Fan Zhang
2018-12-20 12:22 ` [dpdk-dev] [PATCH v4] crypto/aesni_mb: support plain SHA Fan Zhang
2018-12-20 17:52 ` Trahe, Fiona
2019-01-09 22:32 ` De Lara Guarch, Pablo
2019-01-10 14:11 ` De Lara Guarch, Pablo
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=34349130-5efe-0c71-75da-6ea3e6ed1a94@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=damianx.nowak@intel.com \
--cc=dev@dpdk.org \
--cc=lukaszx.krakowiak@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).