From: "Power, Ciara" <ciara.power@intel.com>
To: "O'Donovan, Saoirse" <saoirse.odonovan@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Akhil Goyal <gakhil@marvell.com>,
Fan Zhang <fanzhang.oss@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"O'Donovan, Saoirse" <saoirse.odonovan@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"Doherty, Declan" <declan.doherty@intel.com>
Subject: RE: [PATCH] test/crypto: fix errors for test stats testcase
Date: Mon, 20 Mar 2023 09:40:00 +0000 [thread overview]
Message-ID: <SN7PR11MB76393C79154DB813DA7781D1E6809@SN7PR11MB7639.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230320092956.8576-1-saoirse.odonovan@intel.com>
Hi Saoirse,
> -----Original Message-----
> From: Saoirse O'Donovan <saoirse.odonovan@intel.com>
> Sent: Monday 20 March 2023 09:30
> To: Thomas Monjalon <thomas@monjalon.net>; Akhil Goyal
> <gakhil@marvell.com>; Fan Zhang <fanzhang.oss@gmail.com>
> Cc: dev@dpdk.org; O'Donovan, Saoirse <saoirse.odonovan@intel.com>;
> stable@dpdk.org; Doherty, Declan <declan.doherty@intel.com>
> Subject: [PATCH] test/crypto: fix errors for test stats testcase
>
> The test stats testcase was printing the same error message for multiple errors
> in the test stats testcase. This is now replaced with descriptive error messages,
> which match the cause of the failure.
>
> Fixes: 202d375 ("app/test: add cryptodev unit and performance tests")
> Cc: stable@dpdk.org
> Cc: declan.doherty@intel.com
>
> Signed-off-by: Saoirse O'Donovan <saoirse.odonovan@intel.com>
> ---
> .mailmap | 1 +
> app/test/test_cryptodev.c | 12 ++++++------
> 2 files changed, 7 insertions(+), 6 deletions(-)
Acked-by: Ciara Power <ciara.power@intel.com>
next prev parent reply other threads:[~2023-03-20 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 9:29 Saoirse O'Donovan
2023-03-20 9:40 ` Power, Ciara [this message]
2023-03-28 6:37 ` 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=SN7PR11MB76393C79154DB813DA7781D1E6809@SN7PR11MB7639.namprd11.prod.outlook.com \
--to=ciara.power@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=gakhil@marvell.com \
--cc=saoirse.odonovan@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).