From: Steven Rostedt <rostedt@goodmis.org>
To: linux-trace-devel@vger.kernel.org
Subject: [PATCH 0/2] trace-cmd: Fixes for instance recording and reporting
Date: Fri, 05 Mar 2021 17:47:19 -0500 [thread overview]
Message-ID: <20210305224719.784797597@goodmis.org> (raw)
It appears that the valification code broke instances.
Steven Rostedt (VMware) (2):
trace-cmd record: Allow tracecmd_write_cpu_data() be called multiple times
trace-cmd report: Add last_timestamp array for instances
----
lib/trace-cmd/trace-output.c | 4 +++-
tracecmd/trace-read.c | 12 ++++++------
2 files changed, 9 insertions(+), 7 deletions(-)
next reply other threads:[~2021-03-05 22:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 22:47 Steven Rostedt [this message]
2021-03-05 22:47 ` [PATCH 1/2] trace-cmd record: Allow tracecmd_write_cpu_data() be called multiple times Steven Rostedt
2021-03-05 22:47 ` [PATCH 2/2] trace-cmd report: Add last_timestamp array for instances Steven Rostedt
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=20210305224719.784797597@goodmis.org \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@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).