Re: [GIT PULL 0/5] perf/urgent fixes

From: Ingo Molnar
Date: Tue Dec 08 2015 - 00:10:20 EST



* Arnaldo Carvalho de Melo <acme@xxxxxxxxxx> wrote:

> From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
>
> Hi Ingo,
>
> Please consider applying,
>
> - Arnaldo
>
> The following changes since commit 4e93ad601a4308d4a67673c81556580817d56940:
>
> perf: Do not send exit event twice (2015-12-06 12:54:49 +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 4938cf0c7a62025bbfbf3db7bcdcc2c33312bedb:
>
> perf hists browser: Fix segfault if use symbol filter in cmdline (2015-12-07 12:02:35 -0300)
>
> ----------------------------------------------------------------
> perf/urgent fixes:
>
> User visible:
>
> - Fix showing the running kernel build id using: (Michael Petlan)
>
> $ perf buildid-list -k
> 03c2a89c595616188f02f0282762a75b47069bc0
>
> - hists browser (report, top) symbol filter segfault fixes (Wang Nan)
>
> Signed-off-by: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
>
> ----------------------------------------------------------------
> Michael Petlan (2):
> perf buildid-list: Show running kernel build id fix
> perf buildid-list: Fix return value of perf buildid-list -k
>
> Wang Nan (3):
> perf hists browser: Add NULL pointer check to prevent crash
> perf hists browser: Reset selection when refresh
> perf hists browser: Fix segfault if use symbol filter in cmdline
>
> tools/perf/builtin-buildid-list.c | 2 +-
> tools/perf/ui/browsers/hists.c | 8 ++++++++
> tools/perf/util/build-id.c | 2 +-
> 3 files changed, 10 insertions(+), 2 deletions(-)

Pulled, thanks a lot Arnaldo!

I also merged the fixes into perf/core and pushed it all out, so you can base
subsequent changes on top of the merged result.

Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/