From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH] libtraceevent: Fix a typo in the log man page
Date: Thu, 20 May 2021 06:42:56 +0300 [thread overview]
Message-ID: <20210520034256.355167-1-tz.stoyanov@gmail.com> (raw)
Fixed a typo in the log man page, in the description of the critical
log level.
Signed-off-by: Tzvetomir Stoyanov (VMware) <tz.stoyanov@gmail.com>
---
Documentation/libtraceevent-log.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/libtraceevent-log.txt b/Documentation/libtraceevent-log.txt
index 0aee21d..1ecb4db 100644
--- a/Documentation/libtraceevent-log.txt
+++ b/Documentation/libtraceevent-log.txt
@@ -31,7 +31,7 @@ on the console. Library log levels are:
[verse]
--
_TEP_LOG_NONE_ - Do not print any logs.
- _TEP_LOG_CRITICAL_ - Print critical logs, problem that may case a crash.
+ _TEP_LOG_CRITICAL_ - Print critical logs, problem that may cause a crash.
_TEP_LOG_ERROR_ - Print error logs, problem that could break the main logic of an API.
_TEP_LOG_WARNING_ - Print warnings, problem that could limit the result of an API.
_TEP_LOG_INFO_ - Print information about normal execution of an API.
--
2.31.1
reply other threads:[~2021-05-20 3:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210520034256.355167-1-tz.stoyanov@gmail.com \
--to=tz.stoyanov@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).