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 09/13] tracing: Fix typo in trace_events_trigger.c
Date: Fri, 21 Nov 2025 23:18:31 +0100 [thread overview]
Message-ID: <20251121221835.28032-11-mhi@mailbox.org> (raw)
In-Reply-To: <20251121221835.28032-1-mhi@mailbox.org>
Fix typo "componenents" to "components".
Signed-off-by: Maurice Hieronymus <mhi@mailbox.org>
---
kernel/trace/trace_events_trigger.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/trace/trace_events_trigger.c b/kernel/trace/trace_events_trigger.c
index cbfc306c0159..4f3627060e59 100644
--- a/kernel/trace/trace_events_trigger.c
+++ b/kernel/trace/trace_events_trigger.c
@@ -644,7 +644,7 @@ static void unregister_trigger(char *glob,
* param - text following cmd and ':' and stripped of filter
* filter - the optional filter text following (and including) 'if'
*
- * To illustrate the use of these componenents, here are some concrete
+ * To illustrate the use of these components, here are some concrete
* examples. For the following triggers:
*
* echo 'traceon:5 if pid == 0' > trigger
--
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 ` [PATCH v2 06/13] tracing: Fix multiple typos in trace_events.c Maurice Hieronymus
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 ` Maurice Hieronymus [this message]
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-11-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