From: Mehdi Ben Hadj Khelifa <mehdi.benhadjkhelifa@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, skhan@linuxfoundation.org,
linux-trace-kernel@vger.kernel.org,
mathieu.desnoyers@efficios.com, corbet@lwn.net
Cc: linux-kernel-mentees@lists.linuxfoundation.org,
mhiramat@kernel.org, rostedt@goodmis.org
Subject: Re: [PATCH] docs: Corrected typo in trace/events
Date: Tue, 19 Aug 2025 18:34:49 +0100 [thread overview]
Message-ID: <f5eafdfc-2ecd-4212-bb88-b93c34de7673@gmail.com> (raw)
In-Reply-To: <d14df81f-989f-4467-aa0c-5c65009fd66d@infradead.org>
On 8/19/25 6:18 PM, Randy Dunlap wrote:
>
>
> 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.benhadjkhelifa@gmail.com>
>
> Reviewed-by: Randy Dunlap <rdunlap@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()
>
Thanks for the review Randy,
appreciate your time.
next prev parent reply other threads:[~2025-08-19 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 8:49 [PATCH] docs: Corrected typo in trace/events Mehdi Ben Hadj Khelifa
2025-08-19 17:18 ` Randy Dunlap
2025-08-19 17:34 ` Mehdi Ben Hadj Khelifa [this message]
2025-08-21 17:59 ` Jonathan Corbet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f5eafdfc-2ecd-4212-bb88-b93c34de7673@gmail.com \
--to=mehdi.benhadjkhelifa@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).