DPDK patches and discussions
 help / color / mirror / Atom feed
From: Sunyang Wu <sunyang.wu@jaguarmicro.com>
To: Akhil Goyal <gakhil@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [EXT] [PATCH] test/crypto: fix the bug of wrong debug messages
Date: Thu, 1 Sep 2022 08:02:53 +0000	[thread overview]
Message-ID: <KL1PR0601MB55670AC7C47D28C65B2B6E69907B9@KL1PR0601MB5567.apcprd06.prod.outlook.com> (raw)

Thank you for your reference! 
I hope this email finds you well!

Best wishes,
Sunyang

-----Original Message-----
From: Akhil Goyal <gakhil@marvell.com> 
Sent: Sunday, August 28, 16:58 PM
To: Sunyang Wu <sunyang.wu@jaguarmicro.com>; dev@dpdk.org
Cc: roy.fan.zhang@intel.com; stable@dpdk.org
Subject: RE: [EXT] [PATCH] test/crypto: fix the bug of wrong debug messages

> When the queue_ops_rsa_enc_dec function is called, the plaintext will 
> be printed twice instead of both plaintext and ciphertext. When the 
> create_aead_operation function is called, the contents of iv and aad 
> will be printed incorrectly. This patch fixes the issues above.
> 
> Fixes: 77a217a19bb7 ("test/crypto: add AES-CCM tests")
>        5ae36995f10f ("test/crypto: move RSA enqueue/
> 	                  dequeue into functions")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Sunyang Wu <sunyang.wu@jaguarmicro.com>
> Reviewed-by: Joey Xing <joey.xing@jaguarmicro.com>
> Reviewed-by: Qingmin Liu <qingmin.liu@jaguarmicro.com>
> Reviewed-by: Lei Cai <lei.cai@jaguarmicro.com>
Acked-by: Akhil Goyal <gakhil@marvell.com>

Applied to dpdk-next-crypto

Thanks.

             reply	other threads:[~2022-09-01  8:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01  8:02 Sunyang Wu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-26  3:38 Sunyang Wu
2022-08-28  8:58 ` [EXT] " 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=KL1PR0601MB55670AC7C47D28C65B2B6E69907B9@KL1PR0601MB5567.apcprd06.prod.outlook.com \
    --to=sunyang.wu@jaguarmicro.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=roy.fan.zhang@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).