From: Thomas Monjalon <thomas@monjalon.net>
To: "Huang, Wei" <wei.huang@intel.com>,
"Zhang, Tianfei" <tianfei.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Xu, Rosen" <rosen.xu@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
"nipun.gupta@nxp.com" <nipun.gupta@nxp.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [PATCH v5] raw/ifpga: initialize scalar variable before using
Date: Mon, 07 Mar 2022 23:13:55 +0100 [thread overview]
Message-ID: <5919453.fW5hKsROvD@thomas> (raw)
In-Reply-To: <BL1PR11MB5477B6B78F55C8246B353862E3019@BL1PR11MB5477.namprd11.prod.outlook.com>
28/02/2022 08:58, Zhang, Tianfei:
> From: Huang, Wei <wei.huang@intel.com>
> > Sent: Monday, February 21, 2022 3:52 PM
> > To: dev@dpdk.org; Xu, Rosen <rosen.xu@intel.com>; Zhang, Qi Z
> > <qi.z.zhang@intel.com>; nipun.gupta@nxp.com; hemant.agrawal@nxp.com
> > Cc: stable@dpdk.org; Zhang, Tianfei <tianfei.zhang@intel.com>; Yigit, Ferruh
> > <ferruh.yigit@intel.com>; Huang, Wei <wei.huang@intel.com>
> > Subject: [PATCH v5] raw/ifpga: initialize scalar variable before using
> >
> > Scalar variable sub_brg_bdf may be used uninitialized in function
> > ifpga_rawdev_fill_info(). It is initialized now in this fix.
> >
> > Coverity issue: 375805
> > Fixes: 9c006c45d0c5 ("raw/ifpga: scan PCIe BDF device tree")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Wei Huang <wei.huang@intel.com>
>
> It looks good for me.
>
> Acked-by: Tianfei Zhang <tianfei.zhang@intel.com>
Applied, thanks.
prev parent reply other threads:[~2022-03-07 22:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 3:09 [PATCH v1] raw/ifpga: initialize scalar variable before using Wei Huang
2022-02-18 3:20 ` [PATCH v2] " Wei Huang
2022-02-21 2:20 ` [PATCH v3] " Wei Huang
2022-02-21 2:46 ` Xu, Rosen
2022-02-21 6:34 ` [PATCH v4] " Wei Huang
2022-02-21 7:52 ` [PATCH v5] " Wei Huang
2022-02-28 7:58 ` Zhang, Tianfei
2022-03-07 22:13 ` 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=5919453.fW5hKsROvD@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=nipun.gupta@nxp.com \
--cc=qi.z.zhang@intel.com \
--cc=rosen.xu@intel.com \
--cc=stable@dpdk.org \
--cc=tianfei.zhang@intel.com \
--cc=wei.huang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.