The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ryan Chung <seokwoo.chung130@gmail.com>
To: rostedt@goodmis.org, mhiramat@kernel.org,
	mathieu.desnoyers@efficios.com, corbet@lwn.net
Cc: Ryan Chung <seokwoo.chung130@gmail.com>,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: [PATCH 2/2] trace: fix grammar error in debugging.rst
Date: Sun, 31 Aug 2025 19:17:29 +0900	[thread overview]
Message-ID: <20250831101736.11519-3-seokwoo.chung130@gmail.com> (raw)
In-Reply-To: <20250831101736.11519-1-seokwoo.chung130@gmail.com>

Signed-off-by: Ryan Chung <seokwoo.chung130@gmail.com>
---
 Documentation/trace/debugging.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/trace/debugging.rst b/Documentation/trace/debugging.rst
index d54bc500af80..4d88c346fc38 100644
--- a/Documentation/trace/debugging.rst
+++ b/Documentation/trace/debugging.rst
@@ -59,7 +59,7 @@ There is various methods of acquiring the state of the system when a kernel
 crash occurs. This could be from the oops message in printk, or one could
 use kexec/kdump. But these just show what happened at the time of the crash.
 It can be very useful in knowing what happened up to the point of the crash.
-The tracing ring buffer, by default, is a circular buffer than will
+The tracing ring buffer, by default, is a circular buffer that will
 overwrite older events with newer ones. When a crash happens, the content of
 the ring buffer will be all the events that lead up to the crash.
 
-- 
2.43.0


  parent reply	other threads:[~2025-08-31 10:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-31 10:17 [PATCH 0/2] trace: minor documentation fixes for clarity and Ryan Chung
2025-08-31 10:17 ` [PATCH 1/2] trace: rephrase for clearer documentation Ryan Chung
2025-08-31 10:17 ` Ryan Chung [this message]
2025-09-02 14:28 ` [PATCH 0/2] trace: minor documentation fixes for clarity and Steven Rostedt
2025-09-03 18:25   ` Ryan Chung
2025-09-03 19:52     ` Steven Rostedt
2025-09-03 21:32       ` Jonathan Corbet
  -- strict thread matches above, loose matches on Subject: below --
2025-08-31 10:13 Ryan Chung
2025-08-31 10:13 ` [PATCH 2/2] trace: fix grammar error in debugging.rst Ryan Chung

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=20250831101736.11519-3-seokwoo.chung130@gmail.com \
    --to=seokwoo.chung130@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --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