From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Jiri Olsa <jolsa@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] perf tools: 3 fixes
Date: Fri, 13 Nov 2015 12:24:16 -0300 [thread overview]
Message-ID: <20151113152416.GI7160@kernel.org> (raw)
In-Reply-To: <1447408112-1920-1-git-send-email-adrian.hunter@intel.com>
Em Fri, Nov 13, 2015 at 11:48:29AM +0200, Adrian Hunter escreveu:
> Hi
>
> Here are a 3 fixes. The patches apply cleanly to 4.3, although
> the problems go back further than that.
Thanks for the patches and for the before/after for the rbtree problem,
I reproduced it here, fixes the problem!
- Arnaldo
>
> Adrian Hunter (3):
> perf tools: Fix dso lookup by long name and missing buildids
> perf buildid-list: Requires ordered events
> perf inject: Also re-pipe lost_samples event
>
> tools/perf/builtin-inject.c | 1 +
> tools/perf/util/build-id.c | 1 +
> tools/perf/util/dso.c | 17 +++++++++++++++++
> tools/perf/util/dso.h | 1 +
> tools/perf/util/machine.c | 1 +
> 5 files changed, 21 insertions(+)
>
>
> Regards
> Adrian
prev parent reply other threads:[~2015-11-13 15:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 9:48 [PATCH 0/3] perf tools: 3 fixes Adrian Hunter
2015-11-13 9:48 ` [PATCH 1/3] perf tools: Fix dso lookup by long name and missing buildids Adrian Hunter
2015-11-18 6:18 ` [tip:perf/urgent] perf symbols: " tip-bot for Adrian Hunter
2015-11-13 9:48 ` [PATCH 2/3] perf buildid-list: Requires ordered events Adrian Hunter
2015-11-18 6:19 ` [tip:perf/urgent] " tip-bot for Adrian Hunter
2015-11-13 9:48 ` [PATCH 3/3] perf inject: Also re-pipe lost_samples event Adrian Hunter
2015-11-18 6:19 ` [tip:perf/urgent] " tip-bot for Adrian Hunter
2015-11-13 15:24 ` 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=20151113152416.GI7160@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@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