linux-kernel.vger.kernel.org archive mirror
 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,
	Arnaldo Carvalho de Melo <acme@infradead.org>,
	David Ahern <dsahern@gmail.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@elte.hu>, Mike Galbraith <efault@gmx.de>,
	Paul Mackerras <paulus@samba.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Stephane Eranian <eranian@google.com>,
	arnaldo.melo@gmail.com
Subject: [GIT PULL 0/6] perf/core fixes and improvements
Date: Thu, 13 Oct 2011 12:08:18 -0300	[thread overview]
Message-ID: <1318518504-23299-1-git-send-email-acme@infradead.org> (raw)

Hi Ingo,

        Please consider pulling from:

git://github.com/acmel/linux.git perf/core

Regards,

- Arnaldo

Arnaldo Carvalho de Melo (5):
  perf hists browser: Recalculate browser pointers after resort/decay
  perf hists: Don't free decayed entries if in the annotation browser
  perf ui browser: Handle SIGWINCH
  perf ui browser: Remove ui_browser__add_exit_keys
  perf top: Remove entries from entries_collapsed on decay

Stephane Eranian (1):
  perf hists: Fix compilation when NO_NEWT_SUPPORT is set

 tools/perf/builtin-top.c               |   23 ++++-
 tools/perf/perf.c                      |   24 +++++
 tools/perf/perf.h                      |    2 +
 tools/perf/util/hist.c                 |   24 ++++-
 tools/perf/util/hist.h                 |   11 ++-
 tools/perf/util/sort.h                 |    1 +
 tools/perf/util/ui/browser.c           |  176 ++++++++++++++++++++------------
 tools/perf/util/ui/browser.h           |    9 +-
 tools/perf/util/ui/browsers/annotate.c |   17 +--
 tools/perf/util/ui/browsers/hists.c    |   55 +++-------
 tools/perf/util/ui/browsers/map.c      |    6 +-
 tools/perf/util/ui/helpline.h          |    2 +
 12 files changed, 216 insertions(+), 134 deletions(-)


             reply	other threads:[~2011-10-13 15:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13 15:08 Arnaldo Carvalho de Melo [this message]
2011-10-13 15:08 ` [PATCH 1/6] perf hists browser: Recalculate browser pointers after resort/decay Arnaldo Carvalho de Melo
2011-10-13 15:08 ` [PATCH 2/6] perf hists: Don't free decayed entries if in the annotation browser Arnaldo Carvalho de Melo
2011-10-13 15:08 ` [PATCH 3/6] perf hists: Fix compilation when NO_NEWT_SUPPORT is set Arnaldo Carvalho de Melo
2011-10-13 15:08 ` [PATCH 4/6] perf ui browser: Handle SIGWINCH Arnaldo Carvalho de Melo
2011-10-13 15:08 ` [PATCH 5/6] perf ui browser: Remove ui_browser__add_exit_keys Arnaldo Carvalho de Melo
2011-10-13 15:08 ` [PATCH 6/6] perf top: Remove entries from entries_collapsed on decay Arnaldo Carvalho de Melo
2011-10-14  7:16 ` [GIT PULL 0/6] perf/core fixes and improvements Ingo Molnar
2011-10-14 15:07   ` Arnaldo Carvalho de Melo
  -- strict thread matches above, loose matches on Subject: below --
2011-08-16 14:41 Arnaldo Carvalho de Melo
2011-08-17 21:36 ` Ingo Molnar
2011-08-18 12:43   ` 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=1318518504-23299-1-git-send-email-acme@infradead.org \
    --to=acme@infradead.org \
    --cc=arnaldo.melo@gmail.com \
    --cc=dsahern@gmail.com \
    --cc=efault@gmx.de \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).