All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	David Ahern <dsahern@gmail.com>,
	Javi Merino <javi.merino@arm.com>, Jiri Olsa <jolsa@redhat.com>,
	Juri Lelli <juri.lelli@arm.com>,
	Kapileshwar Singh <kapileshwar.singh@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: [GIT PULL 0/2] perf/urgent fixes
Date: Tue, 22 Sep 2015 12:22:10 -0300	[thread overview]
Message-ID: <1442935332-20791-1-git-send-email-acme@kernel.org> (raw)

Hi Ingo,

	Please consider pulling,

- Arnaldo

The following changes since commit f73e22ab450140830005581c2c7ec389791a1b8d:

  perf: Fix races in computing the header sizes (2015-09-18 09:20:26 +0200)

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 c2e4b24ff848bb180f9b9cd873a38327cd219ad2:

  tools lib traceevent: Fix string handling in heterogeneous arch environments (2015-09-22 11:57:04 -0300)

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

User visible:

- Fix libtraceevent string handling in heterogeneous arch environments (Kapileshwar Singh)

- Avoid infinite loop at buildid processing with no samples in 'perf record' (Mark Rutland)

Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

----------------------------------------------------------------
Kapileshwar Singh (1):
      tools lib traceevent: Fix string handling in heterogeneous arch environments

Mark Rutland (1):
      perf record: Avoid infinite loop at buildid processing with no samples

 tools/lib/traceevent/event-parse.c | 23 ++++++++++++++++++++---
 tools/perf/util/session.c          |  5 ++++-
 2 files changed, 24 insertions(+), 4 deletions(-)

             reply	other threads:[~2015-09-22 15:22 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22 15:22 Arnaldo Carvalho de Melo [this message]
2015-09-22 15:22 ` [PATCH 1/2] perf record: Avoid infinite loop at buildid processing with no samples Arnaldo Carvalho de Melo
2015-09-22 15:22 ` [PATCH 2/2] tools lib traceevent: Fix string handling in heterogeneous arch environments Arnaldo Carvalho de Melo
2015-09-23  7:42 ` [GIT PULL 0/2] perf/urgent fixes Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2018-09-18 15:37 Arnaldo Carvalho de Melo
2018-09-18 15:37 ` Arnaldo Carvalho de Melo
2018-09-19 11:34 ` Ingo Molnar
2017-10-27 19:50 Arnaldo Carvalho de Melo
2017-07-04 19:29 Arnaldo Carvalho de Melo
2017-07-05  7:12 ` Ingo Molnar
2016-03-30 22:13 Arnaldo Carvalho de Melo
2016-03-31  6:28 ` Ingo Molnar
2016-03-24 15:52 Arnaldo Carvalho de Melo
2016-03-25  8:43 ` Ingo Molnar
2016-02-01 17:13 Arnaldo Carvalho de Melo
2015-09-03 16:02 Arnaldo Carvalho de Melo
2015-09-04  9:01 ` Ingo Molnar
2015-07-28 16:09 Arnaldo Carvalho de Melo
2015-07-31  7:59 ` Ingo Molnar
2015-07-15 15:20 Arnaldo Carvalho de Melo
2015-07-17 12:17 ` Ingo Molnar
2015-07-13 19:19 Arnaldo Carvalho de Melo
2015-07-15 11:34 ` Ingo Molnar
2015-05-12 21:18 Arnaldo Carvalho de Melo
2015-05-13  6:22 ` Ingo Molnar
2015-05-05 22:16 Arnaldo Carvalho de Melo
2015-05-06  2:55 ` Ingo Molnar
2014-06-23  7:54 Jiri Olsa
2014-06-25  5:41 ` Ingo Molnar
2014-06-04 13:26 Jiri Olsa
2014-06-05  7:53 ` Ingo Molnar
2014-04-15 13:07 Jiri Olsa
2014-04-15 17:26 ` Ingo Molnar
2014-02-28 21:25 Arnaldo Carvalho de Melo
2014-03-01  9:14 ` Ingo Molnar
2014-02-24 19:10 Arnaldo Carvalho de Melo
2014-02-27 11:49 ` Ingo Molnar
2014-01-23 19:38 Arnaldo Carvalho de Melo
2014-01-25  7:23 ` Ingo Molnar
2013-10-28 14:45 Arnaldo Carvalho de Melo
2013-10-28 14:59 ` Ingo Molnar
2013-01-22 22:07 Arnaldo Carvalho de Melo
2013-01-10 20:44 Arnaldo Carvalho de Melo
2012-10-30 13:02 Arnaldo Carvalho de Melo
2012-11-13 17:55 ` Ingo Molnar
2012-05-02 16:27 Arnaldo Carvalho de Melo
2012-05-02 17:34 ` Ingo Molnar
2012-04-16 20:29 Arnaldo Carvalho de Melo
2011-12-07 15:47 Arnaldo Carvalho de Melo
2011-12-07 22:24 ` Ingo Molnar
2011-11-16 14:51 Arnaldo Carvalho de Melo
2011-12-05  9:33 ` Ingo Molnar
2011-05-26 18:05 Arnaldo Carvalho de Melo
2011-05-26 19:17 ` Ingo Molnar
2011-05-15 16:38 Arnaldo Carvalho de Melo
2011-05-15 17:54 ` Ingo Molnar
2011-04-18 15:23 Arnaldo Carvalho de Melo
2011-04-18 15:36 ` Ingo Molnar
2011-03-30  2:29 Arnaldo Carvalho de Melo
2011-03-30  7:06 ` Ingo Molnar
2011-01-22  1:16 Arnaldo Carvalho de Melo
2011-01-18  1:10 Arnaldo Carvalho de Melo
2011-01-18  8:01 ` Ingo Molnar
2010-12-12 15:16 Arnaldo Carvalho de Melo
2010-07-22 20:36 Arnaldo Carvalho de Melo
2010-07-23  7:07 ` Ingo Molnar
2010-06-01 12:17 Arnaldo Carvalho de Melo
2010-06-02  7:13 ` Ingo Molnar

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=1442935332-20791-1-git-send-email-acme@kernel.org \
    --to=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=adrian.hunter@intel.com \
    --cc=dsahern@gmail.com \
    --cc=javi.merino@arm.com \
    --cc=jolsa@redhat.com \
    --cc=juri.lelli@arm.com \
    --cc=kapileshwar.singh@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.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.