From: Slavomir Kaslev <kaslevs@vmware.com>
To: linux-trace-devel@vger.kernel.org
Cc: rostedt@goodmis.org, ykaradzhov@vmware.com, tstoyanov@vmware.com
Subject: [PATCH v4 0/3] trace-cmd: Resend record --date fix
Date: Fri, 14 Dec 2018 15:57:46 +0200 [thread overview]
Message-ID: <20181214135749.12328-1-kaslevs@vmware.com> (raw)
Resending "trace-cmd record --date" fix while keeping backward compatibility.
Ideally those patches should land together since the last one assumes that all
v3 listeners follow new behavior and don't write options in the trace file.
Changes in v4:
- split tracecmd_attach_cpu_data_fd into smaller functions
- reorder the patches per Steven's request
Changes in v3:
- added Signed-off-by
Changes in v2:
- split into 3 patches for easier reviewing
- fix tracecmd_msg_recv not reading cmd_size bytes it doesn't know about
Slavomir Kaslev (3):
trace-cmd: Prepare for protocol bump to version 3
trace-cmd: Fix record --date flag when sending tracing data to a
listener
trace-cmd: Bump protocol version to v3
include/trace-cmd/trace-cmd.h | 16 ++-
tracecmd/include/trace-msg.h | 6 +-
tracecmd/trace-listen.c | 43 +++++---
tracecmd/trace-msg.c | 198 +++++++++++++++-------------------
tracecmd/trace-output.c | 78 +++++++-------
tracecmd/trace-record.c | 79 +++++++-------
6 files changed, 210 insertions(+), 210 deletions(-)
--
2.19.1
next reply other threads:[~2018-12-14 13:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 13:57 Slavomir Kaslev [this message]
2018-12-14 13:57 ` [PATCH v4 1/3] trace-cmd: Prepare for protocol bump to version 3 Slavomir Kaslev
2018-12-14 13:57 ` [PATCH v4 2/3] trace-cmd: Fix record --date flag when sending tracing data to a listener Slavomir Kaslev
2018-12-14 17:47 ` Steven Rostedt
2018-12-14 13:57 ` [PATCH v4 3/3] trace-cmd: Bump protocol version to v3 Slavomir Kaslev
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=20181214135749.12328-1-kaslevs@vmware.com \
--to=kaslevs@vmware.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tstoyanov@vmware.com \
--cc=ykaradzhov@vmware.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).