diff options
| author | Ryan Chung <seokwoo.chung130@gmail.com> | 2025-08-31 19:17:29 +0900 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2025-09-03 15:31:48 -0600 |
| commit | b65988af71af62b81bbc6af0cbe05b18eaef4da5 (patch) | |
| tree | 784d00c87c636301948e5583fcaa62079cb597fd /Documentation/trace | |
| parent | tracing: rephrase for clearer documentation (diff) | |
| download | linux-b65988af71af62b81bbc6af0cbe05b18eaef4da5.tar.gz linux-b65988af71af62b81bbc6af0cbe05b18eaef4da5.zip | |
tracing: fix grammar error in debugging.rst
Signed-off-by: Ryan Chung <seokwoo.chung130@gmail.com>
Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Link: https://lore.kernel.org/r/20250831101736.11519-3-seokwoo.chung130@gmail.com
Diffstat (limited to 'Documentation/trace')
| -rw-r--r-- | Documentation/trace/debugging.rst | 2 |
1 files changed, 1 insertions, 1 deletions
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. |