From: Thomas Monjalon <thomas@monjalon.net>
To: Liang Ma <liang.j.ma@intel.com>
Cc: dev@dpdk.org, "Hunt, David" <david.hunt@intel.com>,
anatoly.burakov@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] power: fix coverity issue
Date: Thu, 09 May 2019 20:46:43 +0200 [thread overview]
Message-ID: <6623637.b1jnyS1aa0@xps> (raw)
In-Reply-To: <7e2a06bb-03eb-e622-d5cc-4a844c80c178@intel.com>
03/05/2019 11:26, Hunt, David:
> On 8/4/2019 5:19 PM, Liang Ma wrote:
> > Fix the resource leaking issue
> >
> > Coverity issue: 337668
> >
> > Fixes: b60fd5f8b1ce8f0a2c ("power: add bit for high frequency cores")
>
> Confirmed that this issue is resolved by testing on our internel
> Coverity server here, version 8.7.1
>
> Tested-by: David Hunt <david.hunt@intel.com>
Applied, thanks
next prev parent reply other threads:[~2019-05-09 18:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 15:21 [dpdk-dev] [PATCH] " Liang Ma
2019-04-08 15:21 ` Liang Ma
2019-04-08 15:32 ` Hunt, David
2019-04-08 15:32 ` Hunt, David
2019-04-08 16:19 ` [dpdk-dev] [PATCH v2] " Liang Ma
2019-04-08 16:19 ` Liang Ma
2019-05-03 9:26 ` Hunt, David
2019-05-03 9:26 ` Hunt, David
2019-05-09 18:46 ` Thomas Monjalon [this message]
2019-05-09 18:46 ` Thomas Monjalon
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=6623637.b1jnyS1aa0@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=liang.j.ma@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).