DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>,
	"declan.doherty@intel.com" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] crypto/aesni_mb: fix DOCSIS AES-256
Date: Sat, 9 May 2020 21:49:49 +0000	[thread overview]
Message-ID: <VI1PR04MB3168696F5670100BD5AE218DE6A30@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1587649609-67464-1-git-send-email-pablo.de.lara.guarch@intel.com>

> When adding support for DOCSIS AES-256,
> when setting the cipher parameters, all key sizes
> were accepted, but only 128-bit and 256-bit keys
> are supported.
> 
> Fixes: 124d04b43743 ("crypto/aesni_mb: support DOCSIS AES-256")
> 
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> Acked-by: Mairtin o Loingsigh <mairtin.oloingsigh@intel.com>
> ---
Applied to dpdk-next-crypto

Thanks.


      reply	other threads:[~2020-05-09 21:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 13:22 [dpdk-dev] [PATCH] " Pablo de Lara
2020-04-21 13:33 ` De Lara Guarch, Pablo
2020-04-22  9:52 ` O'loingsigh, Mairtin
2020-04-23 13:46 ` [dpdk-dev] [PATCH v2] " Pablo de Lara
2020-05-09 21:49   ` 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=VI1PR04MB3168696F5670100BD5AE218DE6A30@VI1PR04MB3168.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=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).