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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250527100145.1e974c21@gandalf.local.home>
Date: Tue, 27 May 2025 10:01:45 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Runji Liu <runjiliu.tech@...il.com>
Cc: mhiramat@...nel.org, mathieu.desnoyers@...icios.com, corbet@....net,
 linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
 linux-doc@...r.kernel.org
Subject: Re: [PATCH] docs: trace: boottime-trace.rst: fix typo

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

> Replace misspelled "eariler" with "earlier" and drop the stray period
> after "example".
> 
> Signed-off-by: Runji Liu <runjiliu.tech@...il.com>

Acked-by: Steven Rostedt (Google) <rostedt@...dmis.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.)
>  
>