From: Jerin Jacob <jerinjacobk@gmail.com>
To: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-dev <dev@dpdk.org>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>,
Jerin Jacob <jerinj@marvell.com>
Subject: Re: [PATCH] net/cnxk: fix uninitialized local variable
Date: Fri, 18 Feb 2022 10:26:23 +0530 [thread overview]
Message-ID: <CALBAE1Px6ACN4fc592J4OaNe=PfZDE5fF=1XY9jtPvNPzMn4Gg@mail.gmail.com> (raw)
In-Reply-To: <20220212124100.3394466-1-gmuthukrishn@marvell.com>
On Sat, Feb 12, 2022 at 6:11 PM Gowrishankar Muthukrishnan
<gmuthukrishn@marvell.com> wrote:
>
> Fix uninitialized local variable as reported by coverity scan.
>
> Fixes: 6af19a9d89b ("net/cnxk: support meter action to flow destroy")
> Coverity issue: 373630
>
> Signed-off-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
Applied to dpdk-next-net-mrvl/for-next-net. Thanks
> ---
> drivers/net/cnxk/cnxk_ethdev.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/cnxk/cnxk_ethdev.c b/drivers/net/cnxk/cnxk_ethdev.c
> index 945600cdaf..62ffb65cc2 100644
> --- a/drivers/net/cnxk/cnxk_ethdev.c
> +++ b/drivers/net/cnxk/cnxk_ethdev.c
> @@ -177,7 +177,7 @@ nix_meter_fini(struct cnxk_eth_dev *dev)
> struct roc_nix *nix = &dev->nix;
> struct roc_nix_rq *rq;
> uint32_t i;
> - int rc;
> + int rc = 0;
>
> RTE_TAILQ_FOREACH_SAFE(mtr, fms, next, next_mtr) {
> for (i = 0; i < mtr->rq_num; i++) {
> --
> 2.25.1
>
prev parent reply other threads:[~2022-02-18 4:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 12:41 Gowrishankar Muthukrishnan
2022-02-18 4:56 ` Jerin Jacob [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='CALBAE1Px6ACN4fc592J4OaNe=PfZDE5fF=1XY9jtPvNPzMn4Gg@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=gmuthukrishn@marvell.com \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.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).