From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Namhyung Kim <namhyung@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -tip:perf/core 0/8] random tiny perf fixes and cleanups
Date: Mon, 12 Dec 2011 13:22:55 -0200 [thread overview]
Message-ID: <20111212152255.GC2213@infradead.org> (raw)
In-Reply-To: <1323703017-6060-1-git-send-email-namhyung@gmail.com>
Em Tue, Dec 13, 2011 at 12:16:49AM +0900, Namhyung Kim escreveu:
> Hello,
>
> This is a patchset for what I found during a code review.
> As you can see all of these are simple few-liners.
> Please take a look and consider applying them.
Thanks a lot, all seems ok, will apply later today to my perf/core
branch,
- Arnaldo
> Thanks.
>
>
> Namhyung Kim (8):
> perf report: Document '--call-graph' for optional print_limit argument
> perf symbols: Get rid of duplicated snprintf()
> perf symbols: Fix error path on symbol__init()
> perf tools: Fix a memory leak on perf_read_values_destroy
> perf tools: Remove stale git headlines from top comment
> perf events: Tidy up perf_event__preprocess_sample
> perf report: Fix usage string
> perf evlist: Fix error handling on perf_event__mmap
>
> tools/perf/Documentation/perf-report.txt | 5 +++--
> tools/perf/builtin-report.c | 8 ++++----
> tools/perf/util/config.c | 7 -------
> tools/perf/util/event.c | 13 +++++++------
> tools/perf/util/evlist.c | 8 ++++++--
> tools/perf/util/symbol.c | 11 +++--------
> tools/perf/util/usage.c | 5 -----
> tools/perf/util/values.c | 1 +
> 8 files changed, 24 insertions(+), 34 deletions(-)
>
> --
> 1.7.6
prev parent reply other threads:[~2011-12-12 15:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 15:16 Namhyung Kim
2011-12-12 15:16 ` [PATCH 1/8] perf report: Document '--call-graph' for optional print_limit argument Namhyung Kim
2011-12-21 8:42 ` [tip:perf/core] " tip-bot for Namhyung Kim
2011-12-12 15:16 ` [PATCH 2/8] perf symbols: Get rid of duplicated snprintf() Namhyung Kim
2011-12-21 8:43 ` [tip:perf/core] " tip-bot for Namhyung Kim
2011-12-12 15:16 ` [PATCH 3/8] perf symbols: Fix error path on symbol__init() Namhyung Kim
2011-12-21 8:44 ` [tip:perf/core] " tip-bot for Namhyung Kim
2011-12-12 15:16 ` [PATCH 4/8] perf tools: Fix a memory leak on perf_read_values_destroy Namhyung Kim
2011-12-21 8:45 ` [tip:perf/core] " tip-bot for Namhyung Kim
2011-12-12 15:16 ` [PATCH 5/8] perf tools: Remove stale git headlines from top comment Namhyung Kim
2011-12-12 18:03 ` Johannes Schindelin
2011-12-12 18:13 ` Ingo Molnar
2011-12-13 13:52 ` [PATCH UPDATED " Namhyung Kim
2011-12-21 8:46 ` [tip:perf/core] " tip-bot for Namhyung Kim
2011-12-12 15:16 ` [PATCH 6/8] perf events: Tidy up perf_event__preprocess_sample Namhyung Kim
2011-12-21 8:46 ` [tip:perf/core] " tip-bot for Namhyung Kim
2011-12-12 15:16 ` [PATCH 7/8] perf report: Fix usage string Namhyung Kim
2011-12-29 20:46 ` [tip:perf/core] " tip-bot for Namhyung Kim
2011-12-12 15:16 ` [PATCH 8/8] perf evlist: Fix error handling on perf_event__mmap Namhyung Kim
2011-12-12 15:22 ` Arnaldo Carvalho de Melo [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=20111212152255.GC2213@infradead.org \
--to=acme@infradead.org \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome