From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Huang, Wei" <wei.huang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>,
"Xu, Rosen" <rosen.xu@intel.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"Zhang, Tianfei" <tianfei.zhang@intel.com>
Subject: Re: [dpdk-stable] [PATCH v1 0/2] Fix coverity issues reported in DPDK-26381
Date: Thu, 1 Apr 2021 12:17:22 +0000 [thread overview]
Message-ID: <8e131c776fcc46fb8cb44fdd0d91db17@intel.com> (raw)
In-Reply-To: <1615969417-17118-1-git-send-email-wei.huang@intel.com>
> -----Original Message-----
> From: Huang, Wei <wei.huang@intel.com>
> Sent: Wednesday, March 17, 2021 4:24 PM
> To: dev@dpdk.org; Xu, Rosen <rosen.xu@intel.com>; Zhang, Qi Z
> <qi.z.zhang@intel.com>
> Cc: stable@dpdk.org; Zhang, Tianfei <tianfei.zhang@intel.com>; Huang, Wei
> <wei.huang@intel.com>
> Subject: [PATCH v1 0/2] Fix coverity issues reported in DPDK-26381
>
> Below coverity issues are fixed in this patch set.
> 367480, 367482
>
> Wei Huang (2):
> raw/ifpga/base: use untained variable as argument
> raw/ifpga/base: add argument to use untained variable
>
> drivers/raw/ifpga/base/ifpga_fme.c | 15 ++++++++-------
> 1 file changed, 8 insertions(+), 7 deletions(-)
>
> --
> 2.29.2
Applied to dpdk-next-net-intel.
Thanks
Qi
next prev parent reply other threads:[~2021-04-01 12:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 8:23 Wei Huang
2021-03-17 8:23 ` [dpdk-stable] [PATCH v1 1/2] raw/ifpga/base: use untained variable as argument Wei Huang
2021-04-01 7:48 ` Zhang, Tianfei
2021-04-01 8:48 ` Xu, Rosen
2021-04-07 14:57 ` [dpdk-stable] [dpdk-dev] " Ferruh Yigit
2021-03-17 8:23 ` [dpdk-stable] [PATCH v1 2/2] raw/ifpga/base: add argument to use untained variable Wei Huang
2021-04-01 7:48 ` Zhang, Tianfei
2021-04-01 8:48 ` Xu, Rosen
2021-04-01 12:17 ` Zhang, Qi Z [this message]
2021-04-20 8:09 ` [dpdk-stable] [dpdk-dev] [PATCH v1 0/2] Fix coverity issues reported in DPDK-26381 Ferruh Yigit
2021-04-20 9:12 ` Zhang, Qi Z
2021-04-20 9:29 ` Zhang, Qi Z
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=8e131c776fcc46fb8cb44fdd0d91db17@intel.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--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 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).