DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Doherty, Declan" <declan.doherty@intel.com>,
	"O'loingsigh, Mairtin" <mairtin.oloingsigh@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] crypto/aesni_mb: fix DOCSIS AES-256
Date: Tue, 21 Apr 2020 13:33:23 +0000	[thread overview]
Message-ID: <SN6PR11MB310169FC752A2D79EF1F5EF384D50@SN6PR11MB3101.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1587475342-2395-1-git-send-email-pablo.de.lara.guarch@intel.com>

Hi Akhil,

> -----Original Message-----
> From: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Sent: Tuesday, April 21, 2020 2:22 PM
> To: Doherty, Declan <declan.doherty@intel.com>; O'loingsigh, Mairtin
> <mairtin.oloingsigh@intel.com>
> Cc: dev@dpdk.org; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Subject: [PATCH] crypto/aesni_mb: fix DOCSIS AES-256
> 
> 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.
> 
> Fixes: 124d04b43743 ("crypto/aesni_mb: support DOCSIS AES-256")
> 
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>

This can be merged to the commit above before RC1 is out, if there is still time.

Thanks,
Pablo


  reply	other threads:[~2020-04-21 13:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 13:22 Pablo de Lara
2020-04-21 13:33 ` De Lara Guarch, Pablo [this message]
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

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=SN6PR11MB310169FC752A2D79EF1F5EF384D50@SN6PR11MB3101.namprd11.prod.outlook.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=mairtin.oloingsigh@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).