patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Nicolas Chautru <nicolas.chautru@intel.com>,
	dev@dpdk.org, "stable@dpdk.org" <stable@dpdk.org>
Cc: hernan.vargas@intel.com, Vipin.Varghese@amd.com
Subject: Re: [PATCH v2 1/3] test/bbdev: fix build issue with optional build flag
Date: Wed, 7 Dec 2022 09:38:10 +0100	[thread overview]
Message-ID: <a6a84284-53e9-d2c8-118a-40e2df786867@redhat.com> (raw)
In-Reply-To: <20221206191441.12428-2-nicolas.chautru@intel.com>



On 12/6/22 20:14, 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")

You missed to cc stable@dpdk.org.
Added it now.


> 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


       reply	other threads:[~2022-12-07  8:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221206191441.12428-1-nicolas.chautru@intel.com>
     [not found] ` <20221206191441.12428-2-nicolas.chautru@intel.com>
2022-12-07  8:38   ` Maxime Coquelin [this message]
     [not found] ` <20221206191441.12428-3-nicolas.chautru@intel.com>
2022-12-07  8:39   ` [PATCH v2 2/3] " 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=a6a84284-53e9-d2c8-118a-40e2df786867@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=Vipin.Varghese@amd.com \
    --cc=dev@dpdk.org \
    --cc=hernan.vargas@intel.com \
    --cc=nicolas.chautru@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).