DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: "Dooley, Brian" <brian.dooley@intel.com>,
	"Power, Ciara" <ciara.power@intel.com>,
	"Ji, Kai" <kai.ji@intel.com>,
	"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Power, Ciara" <ciara.power@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] crypto/ipsec_mb: fix zuc256 maximum tag length
Date: Sun, 5 Feb 2023 17:33:23 +0000	[thread overview]
Message-ID: <CO6PR18MB448490894363561D817FB02AD8D59@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CO6PR18MB4484D77DB9372E0E4A5047EED8D59@CO6PR18MB4484.namprd18.prod.outlook.com>

> Subject: RE: [PATCH] crypto/ipsec_mb: fix zuc256 maximum tag length
> 
> > >
> > > The AESNI_MB PMD supports 8 and 16 byte tag lengths for ZUC256 when
> > > intel-ipsec-mb version is 1.3 or newer.
> > > The conditional check to enable these tag lengths had the incorrect
> operator,
> > > which enabled 8 and 16 byte tag lengths for versions below 1.2, which is not
> > > supported.
> > >
> > > Fixes: 7babda4316f9 ("crypto/ipsec_mb: support all tag sizes for ZUC-EIA3-
> > > 256")
> > > Cc: pablo.de.lara.guarch@intel.com
> > >
> > > Signed-off-by: Ciara Power <ciara.power@intel.com>
> > Reviewed-by: Brian Dooley <brian.dooley@intel.com>
> Applied to dpdk-next-crypto
> 
Cc: stable@dpdk.org

      reply	other threads:[~2023-02-05 17:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 17:20 Ciara Power
2023-02-02 14:10 ` Dooley, Brian
2023-02-05 17:32   ` Akhil Goyal
2023-02-05 17:33     ` 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=CO6PR18MB448490894363561D817FB02AD8D59@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=brian.dooley@intel.com \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=kai.ji@intel.com \
    --cc=pablo.de.lara.guarch@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).