From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: stable@dpdk.org, bruce.richardson@intel.com,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Nicolas Chautru <nicolas.chautru@intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: Re: [PATCH v3 3/3] bbdev: fix build with MinGW 13
Date: Wed, 10 Sep 2025 15:00:40 +0200 [thread overview]
Message-ID: <4675976.LvFx2qVVIh@thomas> (raw)
In-Reply-To: <20250908212034.699713-4-thomas@monjalon.net>
08/09/2025 23:17, Thomas Monjalon:
> + const char *status_str = rte_bbdev_enqueue_status_str(i);
> + if (status_str == NULL)
> + continue;
> if (q_data->queue_stats.enqueue_status_count[i] > 0)
> fprintf(f, " Enqueue Status Counters %s %" PRIu64 "\n",
> - rte_bbdev_enqueue_status_str(i),
> + status_str,
> q_data->queue_stats.enqueue_status_count[i]);
Coverity is raising another problem in this code,
which was already there:
i should be an enum, not an integer.
I can fix it in the next version.
prev parent reply other threads:[~2025-09-10 13:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250813152829.457463-1-thomas@monjalon.net>
2025-08-13 15:25 ` [PATCH 1/3] bus/pci: " Thomas Monjalon
2025-08-13 15:25 ` [PATCH 2/3] net/mlx5: " Thomas Monjalon
2025-08-14 9:50 ` Dariusz Sosnowski
2025-08-13 15:25 ` [PATCH 3/3] bbdev: wrong fix for " Thomas Monjalon
2025-08-19 13:51 ` Bruce Richardson
[not found] ` <20250827151759.1448018-1-thomas@monjalon.net>
2025-08-27 15:16 ` [PATCH v2 1/3] bus/pci: fix build with " Thomas Monjalon
2025-08-27 15:16 ` [PATCH v2 2/3] net/mlx5: " Thomas Monjalon
2025-08-27 15:16 ` [PATCH v2 3/3] bbdev: wrong fix for " Thomas Monjalon
2025-08-29 5:36 ` Hemant Agrawal
[not found] ` <20250908212034.699713-1-thomas@monjalon.net>
2025-09-08 21:17 ` [PATCH v3 1/3] bus/pci: fix build with " Thomas Monjalon
2025-09-10 12:59 ` Thomas Monjalon
2025-09-08 21:17 ` [PATCH v3 2/3] net/mlx5: " Thomas Monjalon
2025-09-08 21:17 ` [PATCH v3 3/3] bbdev: " Thomas Monjalon
2025-09-10 13:00 ` Thomas Monjalon [this message]
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=4675976.LvFx2qVVIh@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=maxime.coquelin@redhat.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).