Re: [PATCH] docs: trace: boottime-trace.rst: fix typo

[Steven Rostedt <rostedt@goodmis.org>]

On Mon, 26 May 2025 21:40:46 +0800
Runji Liu <runjiliu.tech@gmail.com> wrote:

> 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>

-- Steve

> ---
>  Documentation/trace/boottime-trace.rst | 4 ++--
>  1 file 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.)
>  
>