On 8/19/25 1:49 AM, Mehdi Ben Hadj Khelifa wrote:
> -Changed 'Dyamically' to 'Dynamically' in trace/events.rst
>
> under sections 7.1 and 7.3
>
> Signed-off-by: Mehdi Ben Hadj Khelifa <mehdi.benhadjkhel...@gmail.com>
Reviewed-by: Randy Dunlap <rdun...@infradead.org>
Thanks.
> ---
> Documentation/trace/events.rst | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/trace/events.rst b/Documentation/trace/events.rst
> index 2d88a2acacc0..18d112963dec 100644
> --- a/Documentation/trace/events.rst
> +++ b/Documentation/trace/events.rst
> @@ -629,8 +629,8 @@ following:
> - tracing synthetic events from in-kernel code
> - the low-level "dynevent_cmd" API
>
> -7.1 Dyamically creating synthetic event definitions
> ----------------------------------------------------
> +7.1 Dynamically creating synthetic event definitions
> +----------------------------------------------------
>
> There are a couple ways to create a new synthetic event from a kernel
> module or other kernel code.
> @@ -944,8 +944,8 @@ Note that synth_event_trace_end() must be called at the
> end regardless
> of whether any of the add calls failed (say due to a bad field name
> being passed in).
>
> -7.3 Dyamically creating kprobe and kretprobe event definitions
> ---------------------------------------------------------------
> +7.3 Dynamically creating kprobe and kretprobe event definitions
> +---------------------------------------------------------------
>
> To create a kprobe or kretprobe trace event from kernel code, the
> kprobe_event_gen_cmd_start() or kretprobe_event_gen_cmd_start()
--
~Randy
