From: Namhyung Kim <namhyung@kernel.org>
To: Felipe Pena <felipensp@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Borislav Petkov <bp@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] tools/perf/util: Fix memory leak in trace-event-info.c
Date: Tue, 15 Oct 2013 13:04:00 +0900 [thread overview]
Message-ID: <877gdfb2of.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1381794504-4146-1-git-send-email-felipensp@gmail.com> (Felipe Pena's message of "Mon, 14 Oct 2013 20:48:24 -0300")
On Mon, 14 Oct 2013 20:48:24 -0300, Felipe Pena wrote:
> Fix for a memory leak on tracing_data_get() function when returning NULL explicitly
Acked-by: Namhyung Kim <namhyung@kernel.org>
Thanks,
Namhyung
prev parent reply other threads:[~2013-10-15 4:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 23:48 [PATCH v3] tools/perf/util: Fix memory leak in trace-event-info.c Felipe Pena
2013-10-15 4:04 ` Namhyung Kim [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=877gdfb2of.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=bp@suse.de \
--cc=felipensp@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.