* Arnaldo Carvalho de Melo <a...@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 <a...@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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to