From: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org,
"Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Subject: [PATCH 1/2] libtracefs: Fix typo in documentation
Date: Mon, 21 Jun 2021 11:49:13 +0300 [thread overview]
Message-ID: <20210621084914.336821-1-y.karadz@gmail.com> (raw)
The typo in the name of the API was fixed already, but we need
to change/fix the documentation as well.
Fixes: 5c013e7 (libtracefs: New APIs for trace options)
Fixes: f415871 (libtracefs: Fix typo in function name)
Signed-off-by: Yordan Karadzhov (VMware) <y.karadz@gmail.com>
---
Documentation/libtracefs-option-misc.txt | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/libtracefs-option-misc.txt b/Documentation/libtracefs-option-misc.txt
index 1cd7c88..4258910 100644
--- a/Documentation/libtracefs-option-misc.txt
+++ b/Documentation/libtracefs-option-misc.txt
@@ -3,7 +3,7 @@ libtracefs(3)
NAME
----
-tracefs_option_enable, tracefs_option_diasble, tracefs_option_name -
+tracefs_option_enable, tracefs_option_disable, tracefs_option_name -
Various trace option functions.
SYNOPSIS
@@ -13,7 +13,7 @@ SYNOPSIS
*#include <tracefs.h>*
int *tracefs_option_enable*(struct tracefs_instance pass:[*]_instance_, enum tracefs_option_id _id_);
-int *tracefs_option_diasble*(struct tracefs_instance pass:[*]_instance_, enum tracefs_option_id _id_);
+int *tracefs_option_disable*(struct tracefs_instance pass:[*]_instance_, enum tracefs_option_id _id_);
const char pass:[*]*tracefs_option_name*(enum tracefs_option_id _id_);
--
@@ -24,7 +24,7 @@ This set of APIs can be used to enable and disable ftrace options and to get the
The _tracefs_option_enable()_ function enables the option with _id_ in the given _instance_. If
_instance_ is NULL, the option is enabled in the top trace instance.
-The _tracefs_option_diasble()_ function disables the option with _id_ in the given _instance_. If
+The _tracefs_option_disable()_ function disables the option with _id_ in the given _instance_. If
_instance_ is NULL, the option is disabled in the top trace instance.
The _tracefs_option_name()_ function returns a string, representing the option with _id_. The string
@@ -33,7 +33,7 @@ must *not* be freed.
RETURN VALUE
------------
-The _tracefs_option_enable()_ and _tracefs_option_diasble()_ functions return 0 if the state of the
+The _tracefs_option_enable()_ and _tracefs_option_disable()_ functions return 0 if the state of the
option is set successfully, or -1 in case of an error.
The _tracefs_option_name()_ function returns string with option name, or "unknown" in case of an
@@ -49,7 +49,7 @@ if (tracefs_option_enable(NULL, TRACEFS_OPTION_ANNOTATE)) {
/* Failed to enable annotate option in top trace instance */
}
...
-if (tracefs_option_diasble(NULL, TRACEFS_OPTION_CONTEXT_INFO)) {
+if (tracefs_option_disable(NULL, TRACEFS_OPTION_CONTEXT_INFO)) {
/* Failed to disable context info option in top trace instance */
}
...
--
2.27.0
next reply other threads:[~2021-06-21 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 8:49 Yordan Karadzhov (VMware) [this message]
2021-06-21 8:49 ` [PATCH 2/2] libtracefs: Fix utest compilation Yordan Karadzhov (VMware)
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=20210621084914.336821-1-y.karadz@gmail.com \
--to=y.karadz@gmail.com \
--cc=linux-trace-devel@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;
as well as URLs for NNTP newsgroup(s).