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 05/15] tracing: Fix multiple typos in ring_buffer.c
Date: Fri, 05 Dec 2025 20:06:38 -0500 [thread overview]
Message-ID: <20251206010701.481932137@kernel.org> (raw)
In-Reply-To: 20251206010633.884804695@kernel.org
From: Maurice Hieronymus <mhi@mailbox.org>
Fix multiple typos in comments:
"ording" -> "ordering"
"scatch" -> "scratch"
"wont" -> "won't"
Link: https://patch.msgid.link/20251121221835.28032-5-mhi@mailbox.org
Signed-off-by: Maurice Hieronymus <mhi@mailbox.org>
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
---
kernel/trace/ring_buffer.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
index 8688c88534de..41c9f5d079be 100644
--- a/kernel/trace/ring_buffer.c
+++ b/kernel/trace/ring_buffer.c
@@ -1770,7 +1770,7 @@ static bool rb_meta_init(struct trace_buffer *buffer, int scratch_size)
bmeta->total_size = total_size;
bmeta->buffers_offset = (void *)ptr - (void *)bmeta;
- /* Zero out the scatch pad */
+ /* Zero out the scratch pad */
memset((void *)bmeta + sizeof(*bmeta), 0, bmeta->buffers_offset - sizeof(*bmeta));
return false;
@@ -6089,7 +6089,7 @@ static void rb_clear_buffer_page(struct buffer_page *page)
* id field, and updated via this function.
*
* But for a fixed memory mapped buffer, the id is already assigned for
- * fixed memory ording in the memory layout and can not be used. Instead
+ * fixed memory ordering in the memory layout and can not be used. Instead
* the index of where the page lies in the memory layout is used.
*
* For the normal pages, set the buffer page id with the passed in @id
@@ -7669,7 +7669,7 @@ static __init int test_ringbuffer(void)
/*
* Show buffer is enabled before setting rb_test_started.
* Yes there's a small race window where events could be
- * dropped and the thread wont catch it. But when a ring
+ * dropped and the thread won't catch it. But when a ring
* buffer gets enabled, there will always be some kind of
* delay before other CPUs see it. Thus, we don't care about
* those dropped events. We care about events dropped after
--
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 ` Steven Rostedt [this message]
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 ` [for-linus][PATCH 12/15] tracing: Fix multiple typos in trace_events_user.c Steven Rostedt
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=20251206010701.481932137@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.