From: Huichun Feng <foxhoundsk.tw@gmail.com>
To: corbet@lwn.net
Cc: rostedt@goodmis.org, mingo@redhat.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Huichun Feng <foxhoundsk.tw@gmail.com>,
Ching-Chun Huang <jserv@ccns.ncku.edu.tw>,
Chun-Hung Tseng <henrybear327@gmail.com>
Subject: [PATCH] docs: ftrace: fix ambiguous sentence
Date: Tue, 11 Jan 2022 13:20:01 +0800 [thread overview]
Message-ID: <20220111052000.2675944-1-foxhoundsk.tw@gmail.com> (raw)
The sentence looks ambiguous, rephrase it by adding ", there".
Signed-off-by: Huichun Feng <foxhoundsk.tw@gmail.com>
Signed-off-by: Ching-Chun (Jim) Huang <jserv@ccns.ncku.edu.tw>
Signed-off-by: Chun-Hung Tseng <henrybear327@gmail.com>
---
Documentation/trace/ftrace.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/trace/ftrace.rst b/Documentation/trace/ftrace.rst
index b3166c4a7..45b8c56af 100644
--- a/Documentation/trace/ftrace.rst
+++ b/Documentation/trace/ftrace.rst
@@ -3370,7 +3370,7 @@ one of the latency tracers, you will get the following results.
Instances
---------
-In the tracefs tracing directory is a directory called "instances".
+In the tracefs tracing directory, there is a directory called "instances".
This directory can have new directories created inside of it using
mkdir, and removing directories with rmdir. The directory created
with mkdir in this directory will already contain files and other
--
2.34.1
next reply other threads:[~2022-01-11 5:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 5:20 Huichun Feng [this message]
2022-01-13 22:04 ` [PATCH] docs: ftrace: fix ambiguous sentence Steven Rostedt
2022-01-17 21:56 ` Jonathan Corbet
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=20220111052000.2675944-1-foxhoundsk.tw@gmail.com \
--to=foxhoundsk.tw@gmail.com \
--cc=corbet@lwn.net \
--cc=henrybear327@gmail.com \
--cc=jserv@ccns.ncku.edu.tw \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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).