From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org, mingo@elte.hu
Subject: Re: [PATCH] perf: fix issue with binaries using 16-bytes buildids (v2)
Date: Fri, 9 Sep 2011 14:28:12 -0300 [thread overview]
Message-ID: <20110909172812.GA13072@ghostprotocols.net> (raw)
In-Reply-To: <CABPqkBTvz+WCDCknMn4wzr8LU__N199qaPqKH43q6EHadDKQSg@mail.gmail.com>
Em Fri, Sep 09, 2011 at 07:03:12PM +0200, Stephane Eranian escreveu:
> Arnaldo,
>
> To my surprise, this patch from Last October is STILL not in.
> People are reporting issues with perf related to md5 buildids..
Got it now, thanks for resubmitting, will appear on perf/urgent as soon
as things normalize on kernel.org.
- Arnaldo
- Arnaldo
prev parent reply other threads:[~2011-09-09 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 15:25 [PATCH] perf: fix issue with binaries using 16-bytes buildids (v2) Stephane Eranian
2011-09-09 17:03 ` Stephane Eranian
2011-09-09 17:28 ` Arnaldo Carvalho de Melo [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=20110909172812.GA13072@ghostprotocols.net \
--to=acme@redhat.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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