From: Thomas Monjalon <thomas@monjalon.net>
To: "Kearney, Tadhg" <tadhg.kearney@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Hunt, David" <david.hunt@intel.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
"Pattan, Reshma" <reshma.pattan@intel.com>
Subject: Re: [PATCH] power: fix resource leak by open file pointers
Date: Wed, 26 Oct 2022 23:30:54 +0200 [thread overview]
Message-ID: <2084947.OBFZWjSADL@thomas> (raw)
In-Reply-To: <SN6PR11MB3373915CA1CE598C051FEE00FF299@SN6PR11MB3373.namprd11.prod.outlook.com>
> > Close file pointers to Intel uncore sysfiles.
> >
> > Coverity issue: 381400 381397
> > Fixes: 60b8a661a957 ("power: add Intel uncore frequency control")
> > CC: david.hunt@intel.com
> >
> > Signed-off-by: Tadhg Kearney <tadhg.kearney@intel.com>
> Reviewed-by: Reshma Pattan <reshma.pattan@intel.com>
> Acked-by: Reshma Pattan <reshma.pattan@intel.com>
Applied, thanks.
next prev parent reply other threads:[~2022-10-26 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 8:29 Tadhg Kearney
2022-10-17 8:37 ` Pattan, Reshma
2022-10-26 21:30 ` Thomas Monjalon [this message]
2022-11-04 16:23 ` [PATCH] power: fix double free of opened files Tadhg Kearney
2022-11-07 9:17 ` Pattan, Reshma
2022-11-14 10:00 ` David Marchand
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=2084947.OBFZWjSADL@thomas \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=reshma.pattan@intel.com \
--cc=tadhg.kearney@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).