From: "Yuan, DukaiX" <dukaix.yuan@intel.com>
To: "Sevincer, Abdullah" <abdullah.sevincer@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Pattan, Reshma" <reshma.pattan@intel.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
"Sevincer, Abdullah" <abdullah.sevincer@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH v1] app/procinfo: revise display eventdev xstats
Date: Wed, 12 Jul 2023 02:43:30 +0000 [thread overview]
Message-ID: <CH2PR11MB4487489A7C78EDD7A3257A5BE836A@CH2PR11MB4487.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230708162356.2961843-1-abdullah.sevincer@intel.com>
> -----Original Message-----
> From: Abdullah Sevincer <abdullah.sevincer@intel.com>
> Sent: 2023年7月9日 0:24
> To: dev@dpdk.org
> Cc: Pattan, Reshma <reshma.pattan@intel.com>;
> stephen@networkplumber.org; Sevincer, Abdullah
> <abdullah.sevincer@intel.com>; stable@dpdk.org
> Subject: [PATCH v1] app/procinfo: revise display eventdev xstats
>
> process_eventdev_xstats() function was iterating over eventdev_var[]
> structure even if there is no eventdev present.
> Revised the code to check to iterate and only look for the number of
> eventdevs present in the system. Also, shortened function name to
> eventdev_xstats().
>
> Coverity issue: 395458
> Fixes: 674bb3906931 ("app/procinfo: display eventdev xstats")
> Cc: stable@dpdk.org
>
> Signed-off-by: Abdullah Sevincer <abdullah.sevincer@intel.com>
> ---
Tested-by: Dukai Yuan<dukaix.yuan@intel.com>
next prev parent reply other threads:[~2023-07-12 2:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-08 16:23 Abdullah Sevincer
2023-07-12 2:43 ` Yuan, DukaiX [this message]
2023-07-12 14:22 ` Thomas Monjalon
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=CH2PR11MB4487489A7C78EDD7A3257A5BE836A@CH2PR11MB4487.namprd11.prod.outlook.com \
--to=dukaix.yuan@intel.com \
--cc=abdullah.sevincer@intel.com \
--cc=dev@dpdk.org \
--cc=reshma.pattan@intel.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.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).