From: Steven Rostedt <rostedt@goodmis.org>
To: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Cc: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>,
linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] kernel-shark v2: Change the logic for opening trace-cmd files
Date: Thu, 11 Mar 2021 09:55:23 -0500 [thread overview]
Message-ID: <20210311095523.54934f40@gandalf.local.home> (raw)
In-Reply-To: <42d08f5e-d681-715b-9f40-5763c4332394@gmail.com>
On Thu, 11 Mar 2021 16:15:59 +0200
"Yordan Karadzhov (VMware)" <y.karadz@gmail.com> wrote:
> Have you tested that this works with the Timestamp synchronization
> patches that are not upstreamed yet?
I was in the process of doing so, but haven't done it yet :-/
Will do today.
-- Steve
prev parent reply other threads:[~2021-03-11 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 12:11 [PATCH] kernel-shark v2: Change the logic for opening trace-cmd files Tzvetomir Stoyanov (VMware)
2021-03-10 21:48 ` Steven Rostedt
2021-03-11 14:15 ` Yordan Karadzhov (VMware)
2021-03-11 14:55 ` Steven Rostedt [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=20210311095523.54934f40@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=tz.stoyanov@gmail.com \
--cc=y.karadz@gmail.com \
/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).