[GIT PULL 0/5] perf/urgent fixes

[Arnaldo Carvalho de Melo]

From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxxxxxxxxxx>

Hi Ingo,

	Please consider pulling,

- Arnaldo

The following changes since commit 801a76050bcf8d4e500eb8d048ff6265f37a61c8:

  seq_file: always clear m->count when we free m->buf (2013-11-18 19:07:53 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux tags/perf-urgent-for-mingo

for you to fetch changes up to 6b5fa0ba4f85a8499287aefaf3f1375450c40c6d:

  tools lib traceevent: Fix conversion of pointer to integer of different size (2013-11-19 16:37:59 -0300)

----------------------------------------------------------------
perf/urgent fixes:

. Tag thread comm as overriden, showing the right comm for threads after forks,
  fix from Frederic Weisbecker.

. Fix memory leak when processing perf.data file header, from Namhyung Kim.

. Don't try to free string constant used for anonymous event groups, fix from Namhyung Kim.

. Fix use of multiple options in processing field in libtraceevent, fix from Steven Rostedt.

. Fix conversion of pointer to integer of different size in libtraceevent.

Signed-off-by: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>

----------------------------------------------------------------
Arnaldo Carvalho de Melo (1):
      tools lib traceevent: Fix conversion of pointer to integer of different size

Frederic Weisbecker (1):
      perf tools: Tag thread comm as overriden

Namhyung Kim (2):
      perf header: Fix bogus group name
      perf header: Fix possible memory leaks in process_group_desc()

Steven Rostedt (1):
      tools lib traceevent: Fix use of multiple options in processing field

 tools/lib/traceevent/event-parse.c | 25 ++++++++++++++++++++++---
 tools/perf/util/header.c           |  6 ++++--
 tools/perf/util/thread.c           | 11 +++++------
 3 files changed, 31 insertions(+), 11 deletions(-)
--
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/