aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRunji Liu <runjiliu.tech@gmail.com>2025-05-26 21:40:46 +0800
committerJonathan Corbet <corbet@lwn.net>2025-06-09 14:35:07 -0600
commitea08e53d4d94738f0dfc9e8571d9696cb392600e (patch)
tree8391f7c8037e9026f4549c4db3266c8af80083da
parentdoc: Include scatterlist APIs in htmldocs (diff)
downloadlinux-ea08e53d4d94738f0dfc9e8571d9696cb392600e.tar.gz
linux-ea08e53d4d94738f0dfc9e8571d9696cb392600e.zip
docs: trace: boottime-trace.rst: fix typo
Replace misspelled "eariler" with "earlier" and drop the stray period after "example". Signed-off-by: Runji Liu <runjiliu.tech@gmail.com> Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org> Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org> Signed-off-by: Jonathan Corbet <corbet@lwn.net> Link: https://lore.kernel.org/r/20250526134046.1042-1-runjiliu.tech@gmail.com
-rw-r--r--Documentation/trace/boottime-trace.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/trace/boottime-trace.rst b/Documentation/trace/boottime-trace.rst
index d594597201fd..3efac10adb36 100644
--- a/Documentation/trace/boottime-trace.rst
+++ b/Documentation/trace/boottime-trace.rst
@@ -198,8 +198,8 @@ Most of the subsystems and architecture dependent drivers will be initialized
after that (arch_initcall or subsys_initcall). Thus, you can trace those with
boot-time tracing.
If you want to trace events before core_initcall, you can use the options
-starting with ``kernel``. Some of them will be enabled eariler than the initcall
-processing (for example,. ``kernel.ftrace=function`` and ``kernel.trace_event``
+starting with ``kernel``. Some of them will be enabled earlier than the initcall
+processing (for example, ``kernel.ftrace=function`` and ``kernel.trace_event``
will start before the initcall.)