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>
Subject: Re: [dpdk-stable] [PATCH v2 0/2] raw/ifpga/base: fix defects found by coverity scan
Date: Mon, 9 Nov 2020 09:41:33 +0000 [thread overview]
Message-ID: <6f6ad5dffae54687a6cd2bb8800d6a79@intel.com> (raw)
In-Reply-To: <1604541940-5994-1-git-send-email-wei.huang@intel.com>
> -----Original Message-----
> From: Huang, Wei <wei.huang@intel.com>
> Sent: Thursday, November 5, 2020 10:06 AM
> To: dev@dpdk.org; Xu, Rosen <rosen.xu@intel.com>; Zhang, Qi Z
> <qi.z.zhang@intel.com>
> Cc: stable@dpdk.org; Huang, Wei <wei.huang@intel.com>
> Subject: [PATCH v2 0/2] raw/ifpga/base: fix defects found by coverity scan
>
> Two issues are introduced from previous patch, one resides in ifpga_fme.c and
> the other resides in opae_hw_api.c. Below two patches are provided to fix
> them separately.
>
> Main changes from v2:
> - Fix coding style issue
>
> Wei Huang (2):
> raw/ifpga/base: unlock mutex when nios init fail
> raw/ifpga/base: check pointer adapter before dereference
>
> drivers/raw/ifpga/base/ifpga_fme.c | 2 ++
> drivers/raw/ifpga/base/opae_hw_api.c | 10 ++++++----
> 2 files changed, 8 insertions(+), 4 deletions(-)
>
> --
> 2.29.2
Applied to dpdk-next-net-intel.
Thanks
Qi
prev parent reply other threads:[~2020-11-09 9:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 2:05 Wei Huang
2020-11-05 2:05 ` [dpdk-stable] [PATCH v2 1/2] raw/ifpga/base: unlock mutex when nios init fail Wei Huang
2020-11-05 11:32 ` Xu, Rosen
2020-11-05 2:05 ` [dpdk-stable] [PATCH v2 2/2] raw/ifpga/base: check pointer adapter before dereference Wei Huang
2020-11-05 11:32 ` Xu, Rosen
2020-11-09 9:41 ` Zhang, Qi Z [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=6f6ad5dffae54687a6cd2bb8800d6a79@intel.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=rosen.xu@intel.com \
--cc=stable@dpdk.org \
--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).