DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
	"Ji, Kai" <kai.ji@intel.com>,  "dev@dpdk.org" <dev@dpdk.org>
Cc: "damianx.nowak@intel.com" <damianx.nowak@intel.com>
Subject: Re: [dpdk-dev] test/crypto: fix auth-cipher compare length in oop
Date: Wed, 5 May 2021 15:14:03 +0000	[thread overview]
Message-ID: <MW2PR18MB2284B025F1FAFF51A8562A73D8599@MW2PR18MB2284.namprd18.prod.outlook.com> (raw)
In-Reply-To: <BL0PR11MB3043A3596CD4B2F19030F3FAB85A9@BL0PR11MB3043.namprd11.prod.outlook.com>

> > Subject: [dpdk-dev] test/crypto: fix auth-cipher compare length in oop
> >
> > For out-of-place operations, comparing expected ciphertext with
> > the operation result should skip cipher_offset bytes, as those
> > will not be copied from source to the destination buffer, making
> > the tests fail.
> >
> > Fixes: 02ed7b3871d6 ("test/crypto: add SNOW3G test cases for auth-
> cipher")
> > Cc: damianx.nowak@intel.com
> >
> > Signed-off-by: Kai Ji <kai.ji@intel.com>
> > Signed-off-by: Damian Nowak <damianx.nowak@intel.com>
> > ---
> >  app/test/test_cryptodev.c | 24 ++++++++++++++++--------
> >  1 file changed, 16 insertions(+), 8 deletions(-)
> >
> 
> Welcome Kai!
> 
> Acked-by: Fan Zhang <roy.fan.zhang@intel.com>

Applied to dpdk-next-crypto

Thanks.
PS. This patch was posted twice without superseding. Please take care next time to avoid confusion.

  reply	other threads:[~2021-05-05 15:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-04 14:19 Kai Ji
2021-05-04 16:10 ` Zhang, Roy Fan
2021-05-05 15:14   ` Akhil Goyal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-05-04 13:33 Kai Ji

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=MW2PR18MB2284B025F1FAFF51A8562A73D8599@MW2PR18MB2284.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=damianx.nowak@intel.com \
    --cc=dev@dpdk.org \
    --cc=kai.ji@intel.com \
    --cc=roy.fan.zhang@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).