From: Ingo Molnar <mingo@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
David Ahern <dsahern@gmail.com>, Jiri Olsa <jolsa@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Stephane Eranian <eranian@google.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [GIT PULL 0/3] perf/urgent fixes and improvements
Date: Thu, 1 Jan 2015 22:25:56 +0100 [thread overview]
Message-ID: <20150101212555.GB26239@gmail.com> (raw)
In-Reply-To: <1419348763-29118-1-git-send-email-acme@kernel.org>
* Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> The following changes since commit ac931f87a647ca156f65a4c00e7297165e4fa2d8:
>
> perf: Fix building warning on ARM 32 (2014-12-19 13:09:43 +0100)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-urgent-for-mingo
>
> for you to fetch changes up to 82aa019e0098a1e0801df94345c0297448323126:
>
> perf callchain: Append callchains only when requested (2014-12-23 12:06:39 -0300)
>
> ----------------------------------------------------------------
> perf/urgent fixes and improvements:
>
> User visible:
>
> - Show progress bar in more places while doing histogram processing
> in the hists browser (Namhyung Kim)
>
> - Print backtrace symbols when segfault occurs in 'report' (Namhyung Kim)
>
> Infrastructure:
>
> - Append callchains only when requested (Namhyung Kim)
>
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
>
> ----------------------------------------------------------------
> Namhyung Kim (3):
> perf report: Show progress bar for output resorting
> perf ui/tui: Print backtrace symbols when segfault occurs
> perf callchain: Append callchains only when requested
>
> tools/perf/builtin-annotate.c | 2 +-
> tools/perf/builtin-diff.c | 2 +-
> tools/perf/builtin-report.c | 24 ++++++++++++++++++++++--
> tools/perf/builtin-top.c | 4 ++--
> tools/perf/tests/hists_cumulate.c | 2 +-
> tools/perf/tests/hists_filter.c | 2 +-
> tools/perf/tests/hists_output.c | 10 +++++-----
> tools/perf/ui/tui/setup.c | 26 ++++++++++++++++++++++++--
> tools/perf/util/hist.c | 17 +++++++++++++----
> tools/perf/util/hist.h | 2 +-
> 10 files changed, 71 insertions(+), 20 deletions(-)
Pulled into tip:perf/urgent, thanks a lot Arnaldo!
Ingo
prev parent reply other threads:[~2015-01-01 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 15:32 [GIT PULL 0/3] perf/urgent fixes and improvements Arnaldo Carvalho de Melo
2014-12-23 15:32 ` [PATCH 1/3] perf report: Show progress bar for output resorting Arnaldo Carvalho de Melo
2014-12-23 15:32 ` [PATCH 2/3] perf ui/tui: Print backtrace symbols when segfault occurs Arnaldo Carvalho de Melo
2014-12-23 15:32 ` [PATCH 3/3] perf callchain: Append callchains only when requested Arnaldo Carvalho de Melo
2015-01-01 21:25 ` Ingo Molnar [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=20150101212555.GB26239@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.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.