From: Frederic Weisbecker <fweisbec@gmail.com>
To: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
jkacur@redhat.com, tglx@linutronix.de, mingo@elte.hu
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/core] perf tools: Create util/sort.and use it
Date: Thu, 24 Sep 2009 21:52:48 +0200 [thread overview]
Message-ID: <20090924195246.GA8642@nowhere> (raw)
In-Reply-To: <tip-dd68ada2d417e57b848822a1407b5317a54136c5@git.kernel.org>
On Thu, Sep 24, 2009 at 07:37:05PM +0000, tip-bot for John Kacur wrote:
> Commit-ID: dd68ada2d417e57b848822a1407b5317a54136c5
> Gitweb: http://git.kernel.org/tip/dd68ada2d417e57b848822a1407b5317a54136c5
> Author: John Kacur <jkacur@redhat.com>
> AuthorDate: Thu, 24 Sep 2009 18:02:49 +0200
> Committer: Ingo Molnar <mingo@elte.hu>
> CommitDate: Thu, 24 Sep 2009 21:27:52 +0200
>
> perf tools: Create util/sort.and use it
>
> Create util/sort.[ch] and move common functionality for
> builtin-report.c and builtin-annotate.c there, and make use of it.
>
> Signed-off-by: John Kacur <jkacur@redhat.com>
> LKML-Reference: <alpine.LFD.2.00.0909241758390.11383@localhost.localdomain>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
>
>
> ---
> tools/perf/Makefile | 2 +
> tools/perf/builtin-annotate.c | 211 +---------------------------
> tools/perf/builtin-report.c | 307 +----------------------------------------
> tools/perf/util/sort.c | 268 +++++++++++++++++++++++++++++++++++
> tools/perf/util/sort.h | 93 +++++++++++++
> 5 files changed, 373 insertions(+), 508 deletions(-)
Thanks a lot for this cleanup!
prev parent reply other threads:[~2009-09-24 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 16:02 [PATCH 3/3]Create util/sort.[ch] and use it John Kacur
2009-09-24 16:34 ` John Kacur
2009-09-24 19:37 ` [tip:perf/core] perf tools: Create util/sort.and " tip-bot for John Kacur
2009-09-24 19:52 ` Frederic Weisbecker [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=20090924195246.GA8642@nowhere \
--to=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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