From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Conny Seidel <conny.seidel@amd.com>
Cc: Ingo Molnar <mingo@elte.hu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Petkov, Borislav" <Borislav.Petkov@amd.com>
Subject: Re: [PATCH 1/5] perf tools: Fix fallback to cplus_demangle() when bfd_demangle() is not available
Date: Tue, 6 Jul 2010 10:43:48 -0300 [thread overview]
Message-ID: <20100706134348.GC26192@ghostprotocols.net> (raw)
In-Reply-To: <20100706103103.3b22f53a@marah.osrc.amd.com>
Em Tue, Jul 06, 2010 at 10:31:03AM +0200, Conny Seidel escreveu:
> On Tue, 6 Jul 2010 02:59:04 -0400 Ingo Molnar <mingo@elte.hu> wrote:
> >Since 3.81 is the latest Make version and 3.80 is just one step before
> >that, shouldnt we cherry-pick this into perf/urgent? (or is current
> >upstream unaffected?)
>
> Current upstream is also affected. So it makes sense to put it in
> perf/urgent.
Can you please check if that patch applies to perf/urgent?
- Arnaldo
next prev parent reply other threads:[~2010-07-06 13:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1278378276-25872-1-git-send-email-acme@infradead.org>
2010-07-06 1:04 ` [PATCH 1/5] perf tools: Fix fallback to cplus_demangle() when bfd_demangle() is not available Arnaldo Carvalho de Melo
2010-07-06 6:59 ` Ingo Molnar
2010-07-06 8:31 ` Conny Seidel
2010-07-06 13:43 ` Arnaldo Carvalho de Melo [this message]
2010-07-06 15:39 ` [PATCH tip/perf/urgent] " Conny Seidel
2010-07-06 16:48 ` Arnaldo Carvalho de Melo
2010-07-23 12:12 ` [tip:perf/urgent] " tip-bot for Conny Seidel
2010-07-06 1:04 ` [PATCH 2/5] tracing/kprobes: Support "string" type Arnaldo Carvalho de Melo
2010-07-06 1:04 ` [PATCH 3/5] perf probe: " Arnaldo Carvalho de Melo
2010-07-06 1:04 ` [PATCH 4/5] perf probe: Support tracing an entry of array Arnaldo Carvalho de Melo
2010-07-06 1:04 ` [PATCH 5/5] perf probe: Support static and global variables Arnaldo Carvalho de Melo
2010-07-06 7:03 ` [GIT PULL 0/5] perf/core enhancements and fixes 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=20100706134348.GC26192@ghostprotocols.net \
--to=acme@infradead.org \
--cc=Borislav.Petkov@amd.com \
--cc=conny.seidel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.