From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>,
Akhil Goyal <akhil.goyal@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] crypto/dpaa2_sec: fix HMAC supported key sizes
Date: Thu, 27 Jul 2017 14:25:15 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CBE3714@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <6520377e-bf24-a340-85b4-620b66d91fe9@nxp.com>
> -----Original Message-----
> From: Hemant Agrawal [mailto:hemant.agrawal@nxp.com]
> Sent: Thursday, July 27, 2017 2:58 PM
> To: Akhil Goyal <akhil.goyal@nxp.com>; dev@dpdk.org
> Cc: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>;
> stable@dpdk.org
> Subject: Re: [PATCH] crypto/dpaa2_sec: fix HMAC supported key sizes
>
> On 7/27/2017 5:24 PM, Akhil Goyal 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: 623326dded3a ("crypto/dpaa2_sec: introduce poll mode driver")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com>
...
> >
> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
Applied to dpdk-next-crypto.
Thanks,
Pablo
prev parent reply other threads:[~2017-07-27 14:25 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 ` [dpdk-stable] [PATCH 1/3] crypto/aesni_mb: " Pablo de Lara
2017-07-27 10:22 ` Declan Doherty
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 [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=E115CCD9D858EF4F90C690B0DCB4D8976CBE3714@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.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).