From: Maurice Hieronymus <mhi@mailbox.org>
To: rostedt@goodmis.org, mhiramat@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
mhi@mailbox.org
Subject: [PATCH v2 06/13] tracing: Fix multiple typos in trace_events.c
Date: Fri, 21 Nov 2025 23:18:28 +0100 [thread overview]
Message-ID: <20251121221835.28032-8-mhi@mailbox.org> (raw)
In-Reply-To: <20251121221835.28032-1-mhi@mailbox.org>
Fix multiple typos in comments:
"appened" -> "appended"
"paranthesis" -> "parenthesis"
"parethesis" -> "parenthesis"
"wont" -> "won't"
Signed-off-by: Maurice Hieronymus <mhi@mailbox.org>
---
kernel/trace/trace_events.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c
index 9b07ad9eb284..b16a5a158040 100644
--- a/kernel/trace/trace_events.c
+++ b/kernel/trace/trace_events.c
@@ -360,7 +360,7 @@ static bool process_string(const char *fmt, int len, struct trace_event_call *ca
/* Anything else, this isn't a function */
break;
}
- /* A function could be wrapped in parethesis, try the next one */
+ /* A function could be wrapped in parenthesis, try the next one */
s = r + 1;
} while (s < e);
@@ -567,7 +567,7 @@ static void test_event_printk(struct trace_event_call *call)
* If start_arg is zero, then this is the start of the
* first argument. The processing of the argument happens
* when the end of the argument is found, as it needs to
- * handle paranthesis and such.
+ * handle parenthesis and such.
*/
if (!start_arg) {
start_arg = i;
@@ -785,7 +785,7 @@ static int __ftrace_event_enable_disable(struct trace_event_file *file,
*
* When soft_disable is not set but the soft_mode is,
* we do nothing. Do not disable the tracepoint, otherwise
- * "soft enable"s (clearing the SOFT_DISABLED bit) wont work.
+ * "soft enable"s (clearing the SOFT_DISABLED bit) won't work.
*/
if (soft_disable) {
if (atomic_dec_return(&file->sm_ref) > 0)
@@ -1394,7 +1394,7 @@ int ftrace_set_clr_event(struct trace_array *tr, char *buf, int set)
if (!tr)
return -ENOENT;
- /* Modules events can be appened with :mod:<module> */
+ /* Modules events can be appended with :mod:<module> */
mod = strstr(buf, ":mod:");
if (mod) {
*mod = '\0';
--
2.50.1
next prev parent reply other threads:[~2025-11-21 22:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 22:18 [PATCH v2 00/13] tracing: Fix several comment spelling mistakes Maurice Hieronymus
2025-11-21 22:18 ` [PATCH v2 01/13] tracing: Fix typo in fgraph.c Maurice Hieronymus
2025-11-21 22:18 ` [PATCH v2 01/13] tracing: Fix typo in fpgraph.c Maurice Hieronymus
2025-11-21 22:18 ` [PATCH v2 02/13] tracing: Fix typo in fprobe.c Maurice Hieronymus
2025-11-21 22:18 ` [PATCH v2 03/13] tracing: Fix multiple typos in ring_buffer.c Maurice Hieronymus
2025-11-21 22:18 ` [PATCH v2 04/13] tracing: Fix typo in ring_buffer_benchmark.c Maurice Hieronymus
2025-11-21 22:18 ` [PATCH v2 05/13] tracing: Fix multiple typos in trace.c Maurice Hieronymus
2025-11-21 22:18 ` Maurice Hieronymus [this message]
2025-11-21 22:18 ` [PATCH v2 07/13] tracing: Fix typo in trace_events_filter.c Maurice Hieronymus
2025-11-21 22:18 ` [PATCH v2 08/13] tracing: Fix typo in trace_events_hist.c Maurice Hieronymus
2025-11-21 22:18 ` [PATCH v2 09/13] tracing: Fix typo in trace_events_trigger.c Maurice Hieronymus
2025-11-21 22:18 ` [PATCH v2 10/13] tracing: Fix multiple typos in trace_events_user.c Maurice Hieronymus
2025-11-21 22:18 ` [PATCH v2 11/13] tracing: Fix multiple typos in trace_osnoise.c Maurice Hieronymus
2025-11-21 22:18 ` [PATCH v2 12/13] tracing: Fix typo in trace_probe.c Maurice Hieronymus
2025-11-21 22:18 ` [PATCH v2 13/13] tracing: Fix typo in trace_seq.c Maurice Hieronymus
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=20251121221835.28032-8-mhi@mailbox.org \
--to=mhi@mailbox.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@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