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 15/15] tracing: Fix typo in trace_seq.c
Date: Fri, 05 Dec 2025 20:06:48 -0500 [thread overview]
Message-ID: <20251206010703.189597663@kernel.org> (raw)
In-Reply-To: 20251206010633.884804695@kernel.org
From: Maurice Hieronymus <mhi@mailbox.org>
Fix typo "wont" to "won't".
Link: https://patch.msgid.link/20251121221835.28032-15-mhi@mailbox.org
Signed-off-by: Maurice Hieronymus <mhi@mailbox.org>
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
---
kernel/trace/trace_seq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/trace/trace_seq.c b/kernel/trace/trace_seq.c
index c158d65a8a88..32684ef4fb9d 100644
--- a/kernel/trace/trace_seq.c
+++ b/kernel/trace/trace_seq.c
@@ -15,7 +15,7 @@
*
* A write to the buffer will either succeed or fail. That is, unlike
* sprintf() there will not be a partial write (well it may write into
- * the buffer but it wont update the pointers). This allows users to
+ * the buffer but it won't update the pointers). This allows users to
* try to write something into the trace_seq buffer and if it fails
* they can flush it and try again.
*
--
2.51.0
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 ` [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 ` Steven Rostedt [this message]
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=20251206010703.189597663@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.