From: Declan Doherty <declan.doherty@intel.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>,
zbigniew.bodek@caviumnetworks.com,
jerin.jacob@caviumnetworks.com, akhil.goyal@nxp.com,
hemant.agrawal@nxp.com, fiona.trahe@intel.com,
deepak.k.jain@intel.com, john.griffin@intel.com
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 1/3] crypto/aesni_mb: fix HMAC supported key sizes
Date: Thu, 27 Jul 2017 11:22:19 +0100 [thread overview]
Message-ID: <0e0d15a1-7c5d-bb8f-4e9b-4bfa327b6c0f@intel.com> (raw)
In-Reply-To: <20170725052457.43952-2-pablo.de.lara.guarch@intel.com>
On 25/07/2017 6:24 AM, Pablo de Lara wrote:
> For HMAC algorithms (MD5-HMAC, SHAx-HMAC), the supported
> key sizes are not a fixed value, but a range between
> 1 and the block size.
>
> Fixes: 26c2e4ad5ad4 ("cryptodev: add capabilities discovery")
> Cc: stable@dpdk.org
>
> 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-27 10:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170725052457.43952-1-pablo.de.lara.guarch@intel.com>
2017-07-25 5:24 ` Pablo de Lara
2017-07-27 10:22 ` Declan Doherty [this message]
2017-07-25 5:24 ` [dpdk-stable] [PATCH 2/3] crypto/openssl: " Pablo de Lara
2017-07-27 10:21 ` Declan Doherty
2017-07-25 5:24 ` [dpdk-stable] [PATCH 3/3] crypto/qat: " Pablo de Lara
2017-07-27 9:54 ` Trahe, Fiona
2017-07-27 11:54 ` [dpdk-stable] [PATCH] crypto/dpaa2_sec: " Akhil Goyal
2017-07-27 13:57 ` Hemant Agrawal
2017-07-27 14:25 ` 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=0e0d15a1-7c5d-bb8f-4e9b-4bfa327b6c0f@intel.com \
--to=declan.doherty@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=john.griffin@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=stable@dpdk.org \
--cc=zbigniew.bodek@caviumnetworks.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).