From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] perf intel-pt: Fixes
Date: Tue, 5 Jun 2018 12:32:38 -0300 [thread overview]
Message-ID: <20180605153238.GJ4899@kernel.org> (raw)
In-Reply-To: <1527762225-26024-1-git-send-email-adrian.hunter@intel.com>
Em Thu, May 31, 2018 at 01:23:41PM +0300, Adrian Hunter escreveu:
> Hi
>
> Here are some small non-urgent fixes for Intel PT.
Thanks, applied the kit,
- Arnaldo
>
> Adrian Hunter (4):
> perf intel-pt: Fix sync_switch INTEL_PT_SS_NOT_TRACING
> perf intel-pt: Fix decoding to accept CBR between FUP and corresponding TIP
> perf intel-pt: Fix MTC timing after overflow
> perf intel-pt: Fix "Unexpected indirect branch" error
>
> .../perf/util/intel-pt-decoder/intel-pt-decoder.c | 23 ++++++++++++++++++----
> .../perf/util/intel-pt-decoder/intel-pt-decoder.h | 9 +++++++++
> tools/perf/util/intel-pt.c | 5 +++++
> 3 files changed, 33 insertions(+), 4 deletions(-)
>
>
> Regards
> Adrian
prev parent reply other threads:[~2018-06-05 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 10:23 [PATCH 0/4] perf intel-pt: Fixes Adrian Hunter
2018-05-31 10:23 ` [PATCH 1/4] perf intel-pt: Fix sync_switch INTEL_PT_SS_NOT_TRACING Adrian Hunter
2018-06-07 8:22 ` [tip:perf/urgent] " tip-bot for Adrian Hunter
2018-05-31 10:23 ` [PATCH 2/4] perf intel-pt: Fix decoding to accept CBR between FUP and corresponding TIP Adrian Hunter
2018-06-07 8:22 ` [tip:perf/urgent] " tip-bot for Adrian Hunter
2018-05-31 10:23 ` [PATCH 3/4] perf intel-pt: Fix MTC timing after overflow Adrian Hunter
2018-06-07 8:23 ` [tip:perf/urgent] " tip-bot for Adrian Hunter
2018-05-31 10:23 ` [PATCH 4/4] perf intel-pt: Fix "Unexpected indirect branch" error Adrian Hunter
2018-06-07 8:23 ` [tip:perf/urgent] " tip-bot for Adrian Hunter
2018-06-05 15:32 ` 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=20180605153238.GJ4899@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.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