From: Ingo Molnar <mingo@elte.hu>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Mike Galbraith <efault@gmx.de>,
Brice Goglin <Brice.Goglin@inria.fr>
Subject: Re: [PATCH 1/3] perf tools: Factorize high level dso helpers
Date: Wed, 12 Aug 2009 12:08:51 +0200 [thread overview]
Message-ID: <20090812100851.GA18577@elte.hu> (raw)
In-Reply-To: <20090812095933.GB6081@nowhere>
* Frederic Weisbecker <fweisbec@gmail.com> wrote:
> On Wed, Aug 12, 2009 at 11:26:00AM +0200, Frederic Weisbecker wrote:
> > Factorize multiple definitions of high level dso helpers into the
> > symbol source file.
> >
> > The side effect is a general export of the verbose and eprintf
> > debugging helpers into a new file dedicated to debugging purposes.
> >
> > Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
> > Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
> > Cc: Peter Zijlstra <peterz@infradead.org>
> > Cc: Mike Galbraith <efault@gmx.de>
> > Cc: Brice Goglin <Brice.Goglin@inria.fr>
> > ---
> > tools/perf/Makefile | 1 +
> > tools/perf/builtin-annotate.c | 96 ----------------------------------------
> > tools/perf/builtin-record.c | 1 -
> > tools/perf/builtin-report.c | 97 -----------------------------------------
> > tools/perf/builtin-stat.c | 1 -
> > tools/perf/builtin-top.c | 4 --
> > tools/perf/builtin.h | 1 +
> > tools/perf/perf.h | 1 +
> > tools/perf/util/symbol.c | 97 +++++++++++++++++++++++++++++++++++++++++
> > tools/perf/util/symbol.h | 11 +++++
> > 10 files changed, 111 insertions(+), 199 deletions(-)
> >
> > diff --git a/tools/perf/Makefile b/tools/perf/Makefile
> > index de7beac..2aee21b 100644
> > --- a/tools/perf/Makefile
> > +++ b/tools/perf/Makefile
> > @@ -339,6 +339,7 @@ LIB_OBJS += util/pager.o
> > LIB_OBJS += util/header.o
> > LIB_OBJS += util/callchain.o
> > LIB_OBJS += util/values.o
> > +LIB_OBJS += util/debug.o
>
>
> Damn, did I forgot to git-add util/debug.c ?
>
> How could I fix this? Another pull request?
yeah. I've zapped those commits from perfcounters/core.
Ingo
next prev parent reply other threads:[~2009-08-12 10:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 9:25 [GIT PULL] perf tools: Factorize common code Frederic Weisbecker
2009-08-12 9:26 ` [PATCH 1/3] perf tools: Factorize high level dso helpers Frederic Weisbecker
2009-08-12 9:59 ` Frederic Weisbecker
2009-08-12 10:08 ` Ingo Molnar [this message]
2009-08-12 10:48 ` [GIT PULL v2] perf tools: Factorize common code Frederic Weisbecker
2009-08-12 10:54 ` Ingo Molnar
2009-08-12 11:00 ` Frederic Weisbecker
2009-08-12 13:54 ` Arnaldo Carvalho de Melo
2009-08-12 14:31 ` Ingo Molnar
2009-08-12 10:48 ` [PATCH 1/3 v2] perf tools: Factorize high level dso helpers Frederic Weisbecker
2009-08-12 10:48 ` [PATCH 2/3 v2] perf tools: Factorize the event structure definitions in a single file Frederic Weisbecker
2009-08-12 10:48 ` [PATCH 3/3 v2] perf tools: Factorize the map helpers Frederic Weisbecker
2009-08-12 9:26 ` [PATCH 2/3] perf tools: Factorize the event structure definitions in a single file Frederic Weisbecker
2009-08-12 9:26 ` [PATCH 3/3] perf tools: Factorize the map helpers Frederic Weisbecker
2009-08-12 9:27 ` [GIT PULL] perf tools: Factorize common code Frederic Weisbecker
2009-08-12 9:32 ` Ingo Molnar
2009-08-12 9:52 ` Peter Zijlstra
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=20090812100851.GA18577@elte.hu \
--to=mingo@elte.hu \
--cc=Brice.Goglin@inria.fr \
--cc=acme@redhat.com \
--cc=efault@gmx.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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