From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: gfree.wind@vip.163.com, dev@dpdk.org
Cc: Gao Feng <davidfgao@tencent.com>
Subject: Re: [dpdk-dev] [PATCH] eal: fix memleak on mp request error handler
Date: Mon, 10 Dec 2018 16:38:41 +0000 [thread overview]
Message-ID: <3c80a926-62b5-28c1-a6c9-1c8dcc577aa2@intel.com> (raw)
In-Reply-To: <1543978226-23480-1-git-send-email-gfree.wind@vip.163.com>
On 05-Dec-18 2:50 AM, gfree.wind@vip.163.com wrote:
> From: Gao Feng <davidfgao@tencent.com>
>
> When rte_eal_alarm_set failed, need to free the bundle mem in the
> error handler of handle_primary_request and handle_secondary_request.
>
> Signed-off-by: Gao Feng <davidfgao@tencent.com>
> ---
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-12-10 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 2:50 gfree.wind
2018-12-05 2:50 ` [dpdk-dev] [PATCH] devtools: fix symbol check when adding experimental section gfree.wind
2018-12-05 3:46 ` Gao Feng
2018-12-10 16:38 ` Burakov, Anatoly [this message]
2018-12-19 22:03 ` [dpdk-dev] [PATCH] eal: fix memleak on mp request error handler 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=3c80a926-62b5-28c1-a6c9-1c8dcc577aa2@intel.com \
--to=anatoly.burakov@intel.com \
--cc=davidfgao@tencent.com \
--cc=dev@dpdk.org \
--cc=gfree.wind@vip.163.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).