From: "Vladislav Valtchev (VMware)" <vladislav.valtchev@gmail.com>
To: rostedt@goodmis.org, linux-kernel@vger.kernel.org
Cc: "Vladislav Valtchev (VMware)" <vladislav.valtchev@gmail.com>
Subject: [PATCH 0/3] trace-cmd: fixing three minor user experience issues
Date: Wed, 22 Nov 2017 20:01:59 +0200 [thread overview]
Message-ID: <20171122180202.9519-1-vladislav.valtchev@gmail.com> (raw)
This short patch series fixes three minor user experience issues in trace-cmd:
- an error message (when record is used without -e and -p)
- the documentation of trace record (plugins vs tracers terminology)
- the command 'stat' to report when the stack tracer is enabled
The purpose of this effort is to improve the user experience of the tool.
Vladislav Valtchev (VMware) (3):
trace-cmd: Fix err msg for record w/o the -e option
trace-cmd: s/plugin/tracer/ in record's man page
trace-cmd: Making stat to report when the stack tracer is ON
Documentation/trace-cmd-record.1.txt | 11 +++++------
trace-cmd.h | 3 +++
trace-record.c | 6 ++----
trace-stack.c | 10 ++++++----
trace-stat.c | 11 +++++++----
5 files changed, 23 insertions(+), 18 deletions(-)
--
2.14.1
next reply other threads:[~2017-11-22 18:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 18:01 Vladislav Valtchev (VMware) [this message]
2017-11-22 18:02 ` [PATCH 1/3] trace-cmd: Fix err msg for record w/o the -e option Vladislav Valtchev (VMware)
2017-11-22 18:02 ` [PATCH 2/3] trace-cmd: s/plugin/tracer/ in record's man page Vladislav Valtchev (VMware)
2017-11-22 18:02 ` [PATCH 3/3] trace-cmd: Making stat to report when the stack tracer is ON Vladislav Valtchev (VMware)
2017-11-22 19:50 ` Steven Rostedt
2017-11-23 12:32 ` Vladislav Valtchev
2017-11-29 12:57 ` Steven Rostedt
2017-11-29 14:00 ` Vladislav Valtchev
2017-11-29 16:18 ` Steven Rostedt
2017-11-30 11:26 ` Vladislav Valtchev
2017-11-30 14:56 ` 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=20171122180202.9519-1-vladislav.valtchev@gmail.com \
--to=vladislav.valtchev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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
Powered by JetHome