From: Akhil Goyal <akhil.goyal@nxp.com>
To: Anoob Joseph <anoob.joseph@caviumnetworks.com>,
Declan Doherty <declan.doherty@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: Jerin Jacob <jerin.jacob@caviumnetworks.com>,
Narayana Prasad <narayanaprasad.athreya@caviumnetworks.com>,
dev@dpdk.org, Akash Saxena <akash.saxena@caviumnetworks.com>,
Ayuj Verma <ayuj.verma@caviumnetworks.com>,
stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/3] fix test vector checks
Date: Wed, 26 Sep 2018 17:56:39 +0530 [thread overview]
Message-ID: <f7ba6f27-2675-ba16-993d-82230a06b4fc@nxp.com> (raw)
In-Reply-To: <1536917088-5529-1-git-send-email-anoob.joseph@caviumnetworks.com>
On 9/14/2018 2:54 PM, Anoob Joseph wrote:
> Multiple fixes to the test vector checks.
>
> Anoob Joseph (3):
> app/test-crypto-perf: add checks for AEAD key
> app/test-crypto-perf: fix check for auth key
> app/test-crypto-perf: fix check for cipher IV
>
> app/test-crypto-perf/main.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
patchset applied to dpdk-next-crypto
2/3 and 3/3 for cc: stable@dpdk.org
Thanks
prev parent reply other threads:[~2018-09-26 12:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 9:24 Anoob Joseph
2018-09-14 9:24 ` [dpdk-dev] [PATCH 1/3] app/test-crypto-perf: add checks for AEAD key Anoob Joseph
2018-09-14 9:24 ` [dpdk-dev] [PATCH 2/3] app/test-crypto-perf: fix check for auth key Anoob Joseph
2018-09-14 9:24 ` [dpdk-dev] [PATCH 3/3] app/test-crypto-perf: fix check for cipher IV Anoob Joseph
2018-09-25 14:23 ` [dpdk-dev] [PATCH 0/3] fix test vector checks Akhil Goyal
2018-09-26 12:26 ` Akhil Goyal [this message]
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=f7ba6f27-2675-ba16-993d-82230a06b4fc@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=akash.saxena@caviumnetworks.com \
--cc=anoob.joseph@caviumnetworks.com \
--cc=ayuj.verma@caviumnetworks.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=narayanaprasad.athreya@caviumnetworks.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=stable@dpdk.org \
/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).