]> git.ipfire.org Git - thirdparty/kernel/stable.git/commitdiff
docs: Corrected typo in trace/events
authorMehdi Ben Hadj Khelifa <mehdi.benhadjkhelifa@gmail.com>
Tue, 19 Aug 2025 08:49:00 +0000 (09:49 +0100)
committerJonathan Corbet <corbet@lwn.net>
Thu, 21 Aug 2025 17:59:11 +0000 (11:59 -0600)
-Changed 'Dyamically' to 'Dynamically' in trace/events.rst

under sections 7.1 and 7.3

Signed-off-by: Mehdi Ben Hadj Khelifa <mehdi.benhadjkhelifa@gmail.com>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Link: https://lore.kernel.org/r/20250819085040.974388-1-mehdi.benhadjkhelifa@gmail.com
Documentation/trace/events.rst

index 2d88a2acacc0306227377286710325a92ea34065..18d112963dece7dadf3343c103c9a46f9d15c891 100644 (file)
@@ -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()