From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: "shaikh.kamal" <shaikhkamal2012@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: trace: fprobe: fix 'thos' spelling
Date: Tue, 28 Jul 2026 21:46:45 +0900 [thread overview]
Message-ID: <20260728214645.1e0584e6e654bea696294662@kernel.org> (raw)
In-Reply-To: <20260726065633.20897-1-shaikhkamal2012@gmail.com>
On Sun, 26 Jul 2026 12:26:33 +0530
"shaikh.kamal" <shaikhkamal2012@gmail.com> wrote:
> Fix spelling error reported by codespell: thos -> those.
> No functional change.
>
OK, let me pick it up.
Thanks!
> Signed-off-by: shaikh.kamal <shaikhkamal2012@gmail.com>
> ---
> Documentation/trace/fprobe.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/trace/fprobe.rst b/Documentation/trace/fprobe.rst
> index 95998b189ae3..46dd46a97c1f 100644
> --- a/Documentation/trace/fprobe.rst
> +++ b/Documentation/trace/fprobe.rst
> @@ -118,7 +118,7 @@ will be cancelled.
> @fregs
> This is the `ftrace_regs` data structure at the entry and exit. This
> includes the function parameters, or the return values. So user can
> - access thos values via appropriate `ftrace_regs_*` APIs.
> + access those values via appropriate `ftrace_regs_*` APIs.
>
> @entry_data
> This is a local storage to share the data between entry and exit handlers.
> --
> 2.43.0
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2026-07-28 12:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 6:56 [PATCH] docs: trace: fprobe: fix 'thos' spelling shaikh.kamal
2026-07-28 12:46 ` Masami Hiramatsu [this message]
2026-07-28 13:39 ` shaikh kamaluddin
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=20260728214645.1e0584e6e654bea696294662@kernel.org \
--to=mhiramat@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--cc=shaikhkamal2012@gmail.com \
--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