From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: linux-trace-devel@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>
Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
Subject: [PATCH 3/3] libtracefs: Fix a typo in libtracefs-files
Date: Thu, 29 Jul 2021 16:50:10 +0200 [thread overview]
Message-ID: <0da236ead7e1e7364423f9bcc3c4688d9b313fbb.1627568431.git.bristot@kernel.org> (raw)
In-Reply-To: <cover.1627568431.git.bristot@kernel.org>
s/trasefs/tracefs/
Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
---
Documentation/libtracefs-files.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/libtracefs-files.txt b/Documentation/libtracefs-files.txt
index dc85f2d..d6da507 100644
--- a/Documentation/libtracefs-files.txt
+++ b/Documentation/libtracefs-files.txt
@@ -24,7 +24,7 @@ system mount point and trace files in it.
The _tracefs_get_tracing_file()_ function returns the full path of the
file with given _name_ in the trace file system. The function works
-only with files in the trasefs main directory, it is not trace instance
+only with files in the tracefs main directory, it is not trace instance
aware. It is recommended to use _tracefs_instance_get_file()_ and
_tracefs_instance_get_dir()_ instead. The returned string must be freed
with _tracefs_put_tracing_file()_.
--
2.31.1
next prev parent reply other threads:[~2021-07-29 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 14:50 [PATCH 0/3] libtracefs documentation fixes Daniel Bristot de Oliveira
2021-07-29 14:50 ` [PATCH 1/3] libtracefs: Fix example in libtracefs-events-tep Daniel Bristot de Oliveira
2021-07-29 14:50 ` [PATCH 2/3] libtracefs: Fix example in libtracefs-events Daniel Bristot de Oliveira
2021-07-29 14:50 ` Daniel Bristot de Oliveira [this message]
2021-07-29 19:18 ` [PATCH 0/3] libtracefs documentation fixes 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=0da236ead7e1e7364423f9bcc3c4688d9b313fbb.1627568431.git.bristot@kernel.org \
--to=bristot@kernel.org \
--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).