From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: Vladimir Medvedkin <vladimir.medvedkin@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Dharmik Thakkar <Dharmik.Thakkar@arm.com>,
"stable@dpdk.org" <stable@dpdk.org>,
Yipeng Wang <yipeng1.wang@intel.com>,
Sameh Gobriel <sameh.gobriel@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>, nd <nd@arm.com>
Subject: RE: [PATCH 1/2] test/hash: fix coverity warning
Date: Wed, 9 Nov 2022 08:55:56 +0000 [thread overview]
Message-ID: <AS8PR08MB7080169CC40FE22DB851538A9E3E9@AS8PR08MB7080.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20221103181240.1135012-1-vladimir.medvedkin@intel.com>
> -----Original Message-----
> From: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
> Sent: Friday, November 4, 2022 2:13 AM
> To: dev@dpdk.org
> Cc: Dharmik Thakkar <Dharmik.Thakkar@arm.com>; stable@dpdk.org; Yipeng Wang
> <yipeng1.wang@intel.com>; Sameh Gobriel <sameh.gobriel@intel.com>; Bruce Richardson
> <bruce.richardson@intel.com>
> Subject: [PATCH 1/2] test/hash: fix coverity warning
>
> Remove unnecessary variable assignment
>
> Coverity issue: 336800
> Fixes: 3f9aab961ed3 ("test/hash: check lock-free extendable bucket")
> Cc: dharmik.thakkar@arm.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
> ---
> app/test/test_hash_readwrite_lf_perf.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/app/test/test_hash_readwrite_lf_perf.c
> b/app/test/test_hash_readwrite_lf_perf.c
> index 32f9ec9250..cf86046a2f 100644
> --- a/app/test/test_hash_readwrite_lf_perf.c
> +++ b/app/test/test_hash_readwrite_lf_perf.c
> @@ -1102,7 +1102,6 @@ test_hash_multi_add_lookup(struct rwc_perf *rwc_perf_results, int
> rwc_lf,
> rte_eal_remote_launch(test_rwc_reader,
> (void *)(uintptr_t)read_type,
> enabled_core_ids[i]);
> - write_type = WRITE_KEY_SHIFT;
> pos_core = 0;
>
> /* Launch writers */
> --
> 2.25.1
Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
next prev parent reply other threads:[~2022-11-09 8:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 18:12 Vladimir Medvedkin
2022-11-09 8:55 ` Ruifeng Wang [this message]
2022-11-10 15:13 ` [PATCH v3 " Vladimir Medvedkin
2022-11-14 10:08 ` David Marchand
2022-11-10 15:13 ` [PATCH v3 2/2] " Vladimir Medvedkin
2022-11-10 15:21 ` Bruce Richardson
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=AS8PR08MB7080169CC40FE22DB851538A9E3E9@AS8PR08MB7080.eurprd08.prod.outlook.com \
--to=ruifeng.wang@arm.com \
--cc=Dharmik.Thakkar@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
--cc=sameh.gobriel@intel.com \
--cc=stable@dpdk.org \
--cc=vladimir.medvedkin@intel.com \
--cc=yipeng1.wang@intel.com \
/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).