From: Slavomir Kaslev <kaslevs@vmware.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org, slavomir.kaslev@gmail.com
Subject: [PATCH 0/3] Switch V3 messages to text encoding of variable length buffer
Date: Fri, 15 Mar 2019 17:33:23 +0200 [thread overview]
Message-ID: <20190315153326.5602-1-kaslevs@vmware.com> (raw)
This patchset switches protocol V3 messages to use text encoding for the
variable length buffer at the end as Steven suggested.
Slavomir Kaslev (3):
trace-cmd: Use text encoding for options in protocol V3
trace-cmd: Use text encoding for transmitting ports in protocol V3
trace-cmd: Add msg_buf_len() function
tracecmd/trace-msg.c | 166 ++++++++++++++++++++++++++-----------------
1 file changed, 99 insertions(+), 67 deletions(-)
--
2.19.1
next reply other threads:[~2019-03-15 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 15:33 Slavomir Kaslev [this message]
2019-03-15 15:33 ` [PATCH 1/3] trace-cmd: Use text encoding for options in protocol V3 Slavomir Kaslev
2019-03-15 15:33 ` [PATCH 2/3] trace-cmd: Use text encoding for transmitting ports " Slavomir Kaslev
2019-03-15 15:33 ` [PATCH 3/3] trace-cmd: Add msg_buf_len() function Slavomir Kaslev
2019-03-15 19:08 ` 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=20190315153326.5602-1-kaslevs@vmware.com \
--to=kaslevs@vmware.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=slavomir.kaslev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.