From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Nicolas Chautru <nicolas.chautru@intel.com>,
dev@dpdk.org, thomas@monjalon.net, gakhil@marvell.com
Cc: hernan.vargas@intel.com, Vipin.Varghese@amd.com,
john.mcnamara@intel.com, Ferruh.Yigit@amd.com,
Clinton.France@amd.com
Subject: Re: [PATCH v1 1/2] test/bbdev: fix build issue with optional build flag
Date: Thu, 24 Nov 2022 21:09:27 +0100 [thread overview]
Message-ID: <7ef4430a-a66c-0c97-c138-15a4cb816602@redhat.com> (raw)
In-Reply-To: <20221124160616.6161-2-nicolas.chautru@intel.com>
On 11/24/22 17:06, Nicolas Chautru wrote:
> Incorrect bbdev member name used in test code under
> RTE_BBDEV_OFFLOAD_COST build flag.
>
> Fixes: 4f08028c5e24 ("bbdev: expose queue related warning and status")
>
> Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
> ---
> app/test-bbdev/test_bbdev_perf.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/app/test-bbdev/test_bbdev_perf.c b/app/test-bbdev/test_bbdev_perf.c
> index b285d3f3a7..1859952901 100644
> --- a/app/test-bbdev/test_bbdev_perf.c
> +++ b/app/test-bbdev/test_bbdev_perf.c
> @@ -4933,8 +4933,8 @@ get_bbdev_queue_stats(uint16_t dev_id, uint16_t queue_id,
> stats->dequeued_count = q_stats->dequeued_count;
> stats->enqueue_err_count = q_stats->enqueue_err_count;
> stats->dequeue_err_count = q_stats->dequeue_err_count;
> - stats->enqueue_warning_count = q_stats->enqueue_warning_count;
> - stats->dequeue_warning_count = q_stats->dequeue_warning_count;
> + stats->enqueue_warn_count = q_stats->enqueue_warn_count;
> + stats->dequeue_warn_count = q_stats->dequeue_warn_count;
> stats->acc_offload_cycles = q_stats->acc_offload_cycles;
>
> return 0;
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Thanks,
Maxime
next prev parent reply other threads:[~2022-11-24 20:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 16:06 [PATCH v1 0/2] test/bbdev: fix build issues " Nicolas Chautru
2022-11-24 16:06 ` [PATCH v1 1/2] test/bbdev: fix build issue " Nicolas Chautru
2022-11-24 20:09 ` Maxime Coquelin [this message]
2022-11-24 16:06 ` [PATCH v1 2/2] " Nicolas Chautru
2022-11-24 20:09 ` Maxime Coquelin
2022-12-06 0:18 ` Chautru, Nicolas
2022-12-06 14:46 ` Maxime Coquelin
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=7ef4430a-a66c-0c97-c138-15a4cb816602@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=Clinton.France@amd.com \
--cc=Ferruh.Yigit@amd.com \
--cc=Vipin.Varghese@amd.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=hernan.vargas@intel.com \
--cc=john.mcnamara@intel.com \
--cc=nicolas.chautru@intel.com \
--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).