DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Sivaramakrishnan, VenkatX" <venkatx.sivaramakrishnan@intel.com>
Cc: stable@dpdk.org, "Ji, Kai" <kai.ji@intel.com>,
	"gakhil@marvell.com" <gakhil@marvell.com>,
	"Sivaramakrishnan, VenkatX" <venkatx.sivaramakrishnan@intel.com>,
	"Power, Ciara" <ciara.power@intel.com>,
	dev@dpdk.org
Subject: Re: [PATCH v2] crypto/qat: fix block cipher misalignment for AES CBC and 3DES CBC
Date: Wed, 22 Nov 2023 17:23:37 +0100	[thread overview]
Message-ID: <13392803.dW097sEU6C@thomas> (raw)
In-Reply-To: <DS0PR11MB7631CC9A5BA890EAD27F49E8E6B7A@DS0PR11MB7631.namprd11.prod.outlook.com>

> > check cipher length alignment for 3DES CBC and AES CBC to change it to NULL
> > service type for buffer misalignment.
> > 
> > Fixes: def38073ac90 ("crypto/qat: check cipher buffer alignment")
> > Cc: stable@dpdk.org
> > 
> > Signed-off-by: Sivaramakrishnan Venkat
> > <venkatx.sivaramakrishnan@intel.com>
> > Acked-by: Kai Ji <kai.ji@intel.com>
> > ---
> > v2:
> >     Dropped new tests patch.
> >     Removed settings reponse header directly.
> >     Cleared cookie status instead of setting to SUCCESS.
> 
> Acked-by: Ciara Power <ciara.power@intel.com>

Applied, thanks.




      reply	other threads:[~2023-11-22 16:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03 13:30 [PATCH 1/2] " Sivaramakrishnan Venkat
2023-11-03 13:30 ` [PATCH 2/2] test/crypto: add negative test cases for cipher buffer alignment Sivaramakrishnan Venkat
2023-11-06 23:25   ` Ji, Kai
2023-11-13  7:00   ` [EXT] " Akhil Goyal
2023-11-17  9:38     ` Sivaramakrishnan, VenkatX
2023-11-06 23:24 ` [PATCH 1/2] crypto/qat: fix block cipher misalignment for AES CBC and 3DES CBC Ji, Kai
2023-11-17 12:37 ` [PATCH v2] " Sivaramakrishnan Venkat
2023-11-17 14:43   ` Power, Ciara
2023-11-22 16:23     ` Thomas Monjalon [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=13392803.dW097sEU6C@thomas \
    --to=thomas@monjalon.net \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=kai.ji@intel.com \
    --cc=stable@dpdk.org \
    --cc=venkatx.sivaramakrishnan@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).