From: Steven Rostedt <rostedt@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>,
Maurice Hieronymus <mhi@mailbox.org>
Subject: [for-linus][PATCH 12/15] tracing: Fix multiple typos in trace_events_user.c
Date: Fri, 05 Dec 2025 20:06:45 -0500 [thread overview]
Message-ID: <20251206010702.676651216@kernel.org> (raw)
In-Reply-To: 20251206010633.884804695@kernel.org
From: Maurice Hieronymus <mhi@mailbox.org>
Fix multiple typos in comments:
"ambigious" -> "ambiguous"
"explictly" -> "explicitly"
"Uknown" -> "Unknown"
Link: https://patch.msgid.link/20251121221835.28032-12-mhi@mailbox.org
Signed-off-by: Maurice Hieronymus <mhi@mailbox.org>
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
---
kernel/trace/trace_events_user.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/kernel/trace/trace_events_user.c b/kernel/trace/trace_events_user.c
index b15854c75d4f..dca6e50b3b21 100644
--- a/kernel/trace/trace_events_user.c
+++ b/kernel/trace/trace_events_user.c
@@ -1041,7 +1041,7 @@ static int user_field_array_size(const char *type)
static int user_field_size(const char *type)
{
- /* long is not allowed from a user, since it's ambigious in size */
+ /* long is not allowed from a user, since it's ambiguous in size */
if (strcmp(type, "s64") == 0)
return sizeof(s64);
if (strcmp(type, "u64") == 0)
@@ -1079,7 +1079,7 @@ static int user_field_size(const char *type)
if (str_has_prefix(type, "__rel_loc "))
return sizeof(u32);
- /* Uknown basic type, error */
+ /* Unknown basic type, error */
return -EINVAL;
}
@@ -2465,7 +2465,7 @@ static long user_events_ioctl_reg(struct user_event_file_info *info,
/*
* Prevent users from using the same address and bit multiple times
* within the same mm address space. This can cause unexpected behavior
- * for user processes that is far easier to debug if this is explictly
+ * for user processes that is far easier to debug if this is explicitly
* an error upon registering.
*/
if (current_user_event_enabler_exists((unsigned long)reg.enable_addr,
--
2.51.0
next prev parent reply other threads:[~2025-12-06 1:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-06 1:06 [for-linus][PATCH 00/15] tracing: Fixes for v6.19 Steven Rostedt
2025-12-06 1:06 ` [for-linus][PATCH 01/15] tracing: Fix enabling of tracing on file release Steven Rostedt
2025-12-06 1:06 ` [for-linus][PATCH 02/15] tracing: Fix fixed array of synthetic event Steven Rostedt
2025-12-06 1:06 ` [for-linus][PATCH 03/15] tracing: Fix typo in fpgraph.c Steven Rostedt
2025-12-06 1:06 ` [for-linus][PATCH 04/15] tracing: Fix typo in fprobe.c Steven Rostedt
2025-12-06 1:06 ` [for-linus][PATCH 05/15] tracing: Fix multiple typos in ring_buffer.c Steven Rostedt
2025-12-06 1:06 ` [for-linus][PATCH 06/15] tracing: Fix typo in ring_buffer_benchmark.c Steven Rostedt
2025-12-06 1:06 ` [for-linus][PATCH 07/15] tracing: Fix multiple typos in trace.c Steven Rostedt
2025-12-06 1:06 ` [for-linus][PATCH 08/15] tracing: Fix multiple typos in trace_events.c Steven Rostedt
2025-12-06 1:06 ` [for-linus][PATCH 09/15] tracing: Fix typo in trace_events_filter.c Steven Rostedt
2025-12-06 1:06 ` [for-linus][PATCH 10/15] tracing: Fix typo in trace_events_hist.c Steven Rostedt
2025-12-06 1:06 ` [for-linus][PATCH 11/15] tracing: Fix typo in trace_events_trigger.c Steven Rostedt
2025-12-06 1:06 ` Steven Rostedt [this message]
2025-12-06 1:06 ` [for-linus][PATCH 13/15] tracing: Fix multiple typos in trace_osnoise.c Steven Rostedt
2025-12-06 1:06 ` [for-linus][PATCH 14/15] tracing: Fix typo in trace_probe.c Steven Rostedt
2025-12-06 1:06 ` [for-linus][PATCH 15/15] tracing: Fix typo in trace_seq.c 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=20251206010702.676651216@kernel.org \
--to=rostedt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhi@mailbox.org \
--cc=mhiramat@kernel.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