From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>, linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 01/22] perf intel-pt: Fix itrace defaults for perf script
Date: Mon, 20 May 2019 13:58:09 +0000 [thread overview]
Message-ID: <20190520135810.BDF25216B7@mail.kernel.org> (raw)
In-Reply-To: <20190520113728.14389-2-adrian.hunter@intel.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 90e457f7be08 perf tools: Add Intel PT support.
The bot has tested the following trees: v5.1.3, v5.0.17, v4.19.44, v4.14.120, v4.9.177, v4.4.180.
v5.1.3: Build OK!
v5.0.17: Build OK!
v4.19.44: Failed to apply! Possible dependencies:
4eb068157121 ("perf script: Make itrace script default to all calls")
v4.14.120: Failed to apply! Possible dependencies:
20d9c478b01a ("pert tools: Add queue management functionality")
440a23b34c06 ("perf tools: Add initial entry point for decoder CoreSight traces")
4eb068157121 ("perf script: Make itrace script default to all calls")
68ffe3902898 ("perf tools: Add decoder mechanic to support dumping trace data")
9f878b29da96 ("perf tools: Add full support for CoreSight trace decoding")
b12235b113cf ("perf tools: Add mechanic to synthesise CoreSight trace packets")
ffd3d18c20b8 ("perf tools: Add ARM Statistical Profiling Extensions (SPE) support")
v4.9.177: Failed to apply! Possible dependencies:
20d9c478b01a ("pert tools: Add queue management functionality")
3bdafdffa9ba ("perf auxtrace: Add itrace option to output ptwrite events")
440a23b34c06 ("perf tools: Add initial entry point for decoder CoreSight traces")
4eb068157121 ("perf script: Make itrace script default to all calls")
68ffe3902898 ("perf tools: Add decoder mechanic to support dumping trace data")
70d110d77599 ("perf auxtrace: Add itrace option to output power events")
9f878b29da96 ("perf tools: Add full support for CoreSight trace decoding")
b12235b113cf ("perf tools: Add mechanic to synthesise CoreSight trace packets")
ffd3d18c20b8 ("perf tools: Add ARM Statistical Profiling Extensions (SPE) support")
v4.4.180: Failed to apply! Possible dependencies:
3bdafdffa9ba ("perf auxtrace: Add itrace option to output ptwrite events")
3becf4525d9c ("perf tools: Add sink configuration for cs_etm PMU")
403cacb8a25e ("perf unwind: Don't mix LIBUNWIND_LIBS into LIBUNWIND_LDFLAGS")
440a23b34c06 ("perf tools: Add initial entry point for decoder CoreSight traces")
4eb068157121 ("perf script: Make itrace script default to all calls")
5a155bb77a67 ("perf build: Remove all condition feature check {C,LD}FLAGS")
68ffe3902898 ("perf tools: Add decoder mechanic to support dumping trace data")
70d110d77599 ("perf auxtrace: Add itrace option to output power events")
7e21b0d579a4 ("perf tools: Make coresight PMU listable")
9d8e14d306ef ("perf unwind: Separate local/remote libunwind config")
9f878b29da96 ("perf tools: Add full support for CoreSight trace decoding")
a818c563ae16 ("perf tools: Add coresight etm PMU record capabilities")
b12235b113cf ("perf tools: Add mechanic to synthesise CoreSight trace packets")
d1706b39f0af ("perf tools: Add support for skipping itrace instructions")
ffd3d18c20b8 ("perf tools: Add ARM Statistical Profiling Extensions (SPE) support")
How should we proceed with this patch?
--
Thanks,
Sasha
parent reply other threads:[~2019-05-20 13:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20190520113728.14389-2-adrian.hunter@intel.com>]
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=20190520135810.BDF25216B7@mail.kernel.org \
--to=sashal@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).