From: Declan Doherty <declan.doherty@intel.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 1/2] crypto/aesni_mb: support IPSec Multi-buffer lib v0.46
Date: Mon, 3 Jul 2017 17:03:38 +0100 [thread overview]
Message-ID: <17e29ece-269c-2ab7-cb6a-c6e8e3fa46d0@intel.com> (raw)
In-Reply-To: <20170702025506.35031-2-pablo.de.lara.guarch@intel.com>
On 02/07/17 03:55, Pablo de Lara wrote:
> IPSec Multi-buffer library v0.46 has been released,
> which includes, among othe features, support for 12-byte IV,
> for AES-CTR, keeping also the previous 16-byte IV,
> for backward compatibility reasons.
>
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> ---
...
>
Acked-by: Declan Doherty <declan.doherty@intel.com>
next prev parent reply other threads:[~2017-07-03 16:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 11:48 [dpdk-dev] [PATCH 0/2] AES-NI MB PMD: support Multi-buffer library 0.46 Pablo de Lara
2017-06-28 11:48 ` [dpdk-dev] [PATCH 1/2] crypto/aesni_mb: support IPSec Multi-buffer lib v0.46 Pablo de Lara
2017-06-30 13:52 ` Sergio Gonzalez Monroy
2017-07-02 10:46 ` De Lara Guarch, Pablo
2017-06-28 11:48 ` [dpdk-dev] [PATCH 2/2] test/crypto: add 12-byte IV AES-CTR test cases Pablo de Lara
2017-07-02 2:55 ` [dpdk-dev] [PATCH v2 0/2] AES-NI MB PMD: support Multi-buffer library 0.46 Pablo de Lara
2017-07-02 2:55 ` [dpdk-dev] [PATCH v2 1/2] crypto/aesni_mb: support IPSec Multi-buffer lib v0.46 Pablo de Lara
2017-07-03 16:03 ` Declan Doherty [this message]
2017-07-02 2:55 ` [dpdk-dev] [PATCH v2 2/2] test/crypto: add 12-byte IV AES-CTR test cases Pablo de Lara
2017-07-03 16:03 ` Declan Doherty
2017-07-03 20:22 ` [dpdk-dev] [PATCH v2 0/2] AES-NI MB PMD: support Multi-buffer library 0.46 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=17e29ece-269c-2ab7-cb6a-c6e8e3fa46d0@intel.com \
--to=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@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).