From: Leo Yan <leo.yan@linaro.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Steve MacLean <Steve.MacLean@Microsoft.com>,
Yonatan Goldschmidt <yonatan.goldschmidt@granulate.io>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Kan Liang <kan.liang@linux.intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] perf: Allow TIME_CONV to be backwards-compatible and dump it
Date: Wed, 28 Apr 2021 20:10:37 +0800 [thread overview]
Message-ID: <20210428121037.GA5939@leoy-ThinkPad-X240s> (raw)
In-Reply-To: <20210428115749.5229-1-leo.yan@linaro.org>
On Wed, Apr 28, 2021 at 07:57:45PM +0800, Leo Yan wrote:
> The event PERF_RECORD_TIME_CONV was extended for clock parameters, but
> the tool fails to be backwards-compatible for the old event format.
Please ignore this patch series and directly review patch set v3. Sorry
for noise.
Thanks,
Leo
prev parent reply other threads:[~2021-04-28 12:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 11:57 Leo Yan
2021-04-28 11:57 ` [PATCH v2 1/4] perf tool: Change fields type in cap_user_time_short Leo Yan
2021-04-28 11:57 ` [PATCH v2 2/4] perf jit: Let convert_timestamp() to be backwards-compatible Leo Yan
2021-04-28 11:57 ` [PATCH v2 3/4] perf session: Add swap operation for event TIME_CONV Leo Yan
2021-04-28 11:57 ` [PATCH v2 4/4] perf session: Dump PERF_RECORD_TIME_CONV event Leo Yan
2021-04-28 12:10 ` Leo Yan [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=20210428121037.GA5939@leoy-ThinkPad-X240s \
--to=leo.yan@linaro.org \
--cc=Steve.MacLean@Microsoft.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=gustavoars@kernel.org \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=yonatan.goldschmidt@granulate.io \
/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
all inboxes | Powered by JetHome®