All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
	"Frédéric Weisbecker" <fweisbec@gmail.com>,
	"Mike Galbraith" <efault@gmx.de>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
	"Paul Mackerras" <paulus@samba.org>
Subject: Re: [PATCH 5/6] perf tools: Use rb_for_each_entry
Date: Wed, 13 Jan 2010 10:58:10 -0200	[thread overview]
Message-ID: <20100113125810.GC2934@ghostprotocols.net> (raw)
In-Reply-To: <20100113091135.GE24475@elte.hu>

Em Wed, Jan 13, 2010 at 10:11:35AM +0100, Ingo Molnar escreveu:
> 
> * Arnaldo Carvalho de Melo <acme@infradead.org> wrote:
> 
> > From: Arnaldo Carvalho de Melo <acme@redhat.com>
> > 
> > Cc: Fr??d??ric Weisbecker <fweisbec@gmail.com>
> > Cc: Mike Galbraith <efault@gmx.de>
> > Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > Cc: Paul Mackerras <paulus@samba.org>
> > Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> > ---
> >  tools/perf/builtin-annotate.c |   19 ++++++-------------
> >  tools/perf/builtin-diff.c     |    5 ++---
> >  tools/perf/builtin-kmem.c     |   12 +++++-------
> >  tools/perf/builtin-sched.c    |   10 ++--------
> >  tools/perf/builtin-top.c      |   10 +++-------
> >  tools/perf/util/symbol.c      |   16 ++++++----------
> >  6 files changed, 24 insertions(+), 48 deletions(-)
> 
> hm, this one doesnt build very well:
> 
> touch .perf.dev.null
>     CC builtin-annotate.o
>     CC builtin-diff.o
>     CC builtin-sched.o
>     CC builtin-top.o
>     CC builtin-kmem.o
>     CC util/symbol.o
> cc1: warnings being treated as errors
> builtin-diff.c: In function 'perf_session__match_hists':
> builtin-diff.c:148: error: implicit declaration of function 'rb_for_each_entry'

Checking and will resend shortly.

- Arnaldo

  reply	other threads:[~2010-01-13 12:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07 21:59 [PATCH 1/6] perf buildid-list: No need to process the header sections again Arnaldo Carvalho de Melo
2010-01-07 21:59 ` [PATCH 2/6] perf symbols: Record the domain of DSOs in HEADER_BUILD_ID header table Arnaldo Carvalho de Melo
2010-01-07 21:59 ` [PATCH 3/6] perf tools: Create typedef for common event synthesizing callback Arnaldo Carvalho de Melo
2010-01-07 21:59 ` [PATCH 4/6] rbtree: Introduce rb_for_each_entry Arnaldo Carvalho de Melo
2010-01-07 21:59 ` [PATCH 5/6] perf tools: Use rb_for_each_entry Arnaldo Carvalho de Melo
2010-01-13  9:11   ` Ingo Molnar
2010-01-13 12:58     ` Arnaldo Carvalho de Melo [this message]
2010-01-07 21:59 ` [PATCH 6/6] perf tools: Encode kernel module mappings in perf.data Arnaldo Carvalho de Melo

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=20100113125810.GC2934@ghostprotocols.net \
    --to=acme@infradead.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=efault@gmx.de \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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.