From: Ingo Molnar <mingo@kernel.org>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Albert Strasheim <albert@cloudflare.com>,
Ben Hutchings <ben@decadent.org.uk>,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
David Ahern <dsahern@gmail.com>, Don Zickus <dzickus@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Jiri Olsa <jolsa@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
stable@vger.kernel.org, Stephane Eranian <eranian@google.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [GIT PULL 0/3] perf/urgent fixes
Date: Tue, 11 Mar 2014 11:04:06 +0100 [thread overview]
Message-ID: <20140311100406.GA32500@gmail.com> (raw)
In-Reply-To: <1394486108-5974-1-git-send-email-acme@infradead.org>
* Arnaldo Carvalho de Melo <acme@infradead.org> wrote:
> From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
>
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> The following changes since commit af76815a31adc75dd9526230affdd678e65ac59f:
>
> Merge tag 'perf-urgent-for-mingo' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/urgent (2014-03-01 10:13:25 +0100)
>
> 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 fdf57dd052d5cbd415533ae98f4d423286a85220:
>
> perf machine: Use map as success in ip__resolve_ams (2014-03-10 11:19:36 -0300)
>
> ----------------------------------------------------------------
> perf/urgent fixes:
>
> . Fix build of 'trace' in some systems due to using some architecture-specific
> signal numbers (Ben Hutchings)
>
> . Stop resolving when finding a map in in ip__resolve_ams, this way at least
> the DSO will be resolved when a symbol isn't (Don Zickus)
>
> . Fix crash in elf_section_by_name when not checking if some section string index
> is valid (Jiri Olsa)
>
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
>
> ----------------------------------------------------------------
> Ben Hutchings (1):
> perf trace: Decode architecture-specific signal numbers
>
> Don Zickus (1):
> perf machine: Use map as success in ip__resolve_ams
>
> Jiri Olsa (1):
> perf symbols: Fix crash in elf_section_by_name
>
> tools/perf/builtin-trace.c | 10 +++++++++-
> tools/perf/util/machine.c | 2 +-
> tools/perf/util/symbol-elf.c | 6 +++---
> 3 files changed, 13 insertions(+), 5 deletions(-)
Pulled, thanks a lot Arnaldo!
Ingo
prev parent reply other threads:[~2014-03-11 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 21:15 [GIT PULL 0/3] perf/urgent fixes Arnaldo Carvalho de Melo
2014-03-10 21:15 ` [PATCH 1/3] perf trace: Decode architecture-specific signal numbers Arnaldo Carvalho de Melo
2014-03-11 10:04 ` 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=20140311100406.GA32500@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=acme@infradead.org \
--cc=acme@redhat.com \
--cc=albert@cloudflare.com \
--cc=ben@decadent.org.uk \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=dsahern@gmail.com \
--cc=dzickus@redhat.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).