patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] crypto/qat: fix digest length in XCBC capability
Date: Fri, 13 Sep 2019 11:03:35 +0000	[thread overview]
Message-ID: <06EE24DD0B19E248B53F6DC8657831551B29999D@hasmsx109.ger.corp.intel.com> (raw)
In-Reply-To: <1568133130-18757-1-git-send-email-fiona.trahe@intel.com>



> -----Original Message-----
> From: Trahe, Fiona
> Sent: Tuesday, September 10, 2019 6:32 PM
> To: dev@dpdk.org
> Cc: akhil.goyal@nxp.com; Trahe, Fiona <fiona.trahe@intel.com>; Kusztal,
> ArkadiuszX <arkadiuszx.kusztal@intel.com>; stable@dpdk.org
> Subject: [PATCH] crypto/qat: fix digest length in XCBC capability
> 
> Digest length in RTE_CRYPTO_AUTH_AES_XCBC_MAC capability was
> incorrectly marked 16 bytes, should be 12.
> 
> Fixes: 6a3c87bc6a6c ("crypto/qat: refactor capabilities infrastructure")
> cc: stable@dpdk.org
> 
> Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
> ---
>  drivers/crypto/qat/qat_sym_capabilities.h |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/crypto/qat/qat_sym_capabilities.h
> b/drivers/crypto/qat/qat_sym_capabilities.h
> index 6df12b9..a7fb6a0 100644
> --- a/drivers/crypto/qat/qat_sym_capabilities.h
> +++ b/drivers/crypto/qat/qat_sym_capabilities.h
> @@ -145,8 +145,8 @@
>  					.increment = 0			\
>  				},					\
>  				.digest_size = {			\
> -					.min = 16,			\
> -					.max = 16,			\
> +					.min = 12,			\
> +					.max = 12,			\
>  					.increment = 0			\
>  				},					\
>  				.aad_size = { 0 },			\
> --
> 1.7.0.7

Acked-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>

  reply	other threads:[~2019-09-13 11:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-10 16:32 Fiona Trahe
2019-09-13 11:03 ` Kusztal, ArkadiuszX [this message]
2019-09-19 15:12   ` 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=06EE24DD0B19E248B53F6DC8657831551B29999D@hasmsx109.ger.corp.intel.com \
    --to=arkadiuszx.kusztal@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.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).