Received-SPF: pass (google.com: domain of linux-kernel+bounces-165880-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Date: Thu, 2 May 2024 07:38:56 +0700
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Saurav Shah <sauravshah.31@gmail.com>, rostedt@goodmis.org,
	mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
	mark.rutland@arm.com, corbet@lwn.net
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, Mao Zhu <zhumao001@208suo.com>,
	Ran Sun <sunran001@208suo.com>, Xiang wangx <wangxiang@cdjrlc.com>,
	Shaomin Deng <dengshaomin@cdjrlc.com>,
	Charles Han <hanchunchao@inspur.com>,
	Attreyee M <tintinm2017@gmail.com>
Subject: Re: [PATCH] Documentation: tracing: Fix spelling mistakes
Message-ID: <ZjLgoMzTsyFoR03R@archie.me>
References: <20240501233659.25441-1-sauravshah.31@gmail.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="+qpWXA4C62hzXlBX"
Content-Disposition: inline
In-Reply-To: <20240501233659.25441-1-sauravshah.31@gmail.com>


--+qpWXA4C62hzXlBX
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, May 02, 2024 at 05:06:59AM +0530, Saurav Shah wrote:
> diff --git a/Documentation/trace/fprobetrace.rst b/Documentation/trace/fp=
robetrace.rst
> index 0f187e3796e4..b4c2ca3d02c1 100644
> --- a/Documentation/trace/fprobetrace.rst
> +++ b/Documentation/trace/fprobetrace.rst
> @@ -74,7 +74,7 @@ Function arguments at exit
>  --------------------------
>  Function arguments can be accessed at exit probe using $arg<N> fetcharg.=
 This
>  is useful to record the function parameter and return value at once, and
> -trace the difference of structure fields (for debuging a function whethe=
r it
> +trace the difference of structure fields (for debugging a function wheth=
er it
>  correctly updates the given data structure or not)
>  See the :ref:`sample<fprobetrace_exit_args_sample>` below for how it wor=
ks.
> =20
> @@ -248,4 +248,4 @@ mode. You can trace that changes with return probe.
>               cat-143     [007] ...1.  1945.720616: vfs_open__entry: (vfs=
_open+0x4/0x40) mode=3D0x1 inode=3D0x0
>               cat-143     [007] ...1.  1945.728263: vfs_open__exit: (do_o=
pen+0x274/0x3d0 <- vfs_open) mode=3D0xa800d inode=3D0xffff888004ada8d8
> =20
> -You can see the `file::f_mode` and `file::f_inode` are upated in `vfs_op=
en()`.
> +You can see the `file::f_mode` and `file::f_inode` are updated in `vfs_o=
pen()`.
> diff --git a/Documentation/trace/ftrace.rst b/Documentation/trace/ftrace.=
rst
> index 7e7b8ec17934..5aba74872ba7 100644
> --- a/Documentation/trace/ftrace.rst
> +++ b/Documentation/trace/ftrace.rst
> @@ -1968,7 +1968,7 @@ wakeup
>  One common case that people are interested in tracing is the
>  time it takes for a task that is woken to actually wake up.
>  Now for non Real-Time tasks, this can be arbitrary. But tracing
> -it none the less can be interesting.=20
> +it nonetheless can be interesting.=20
> =20
>  Without function tracing::
> =20
> diff --git a/Documentation/trace/kprobetrace.rst b/Documentation/trace/kp=
robetrace.rst
> index a49662ccd53c..69cb7776ae99 100644
> --- a/Documentation/trace/kprobetrace.rst
> +++ b/Documentation/trace/kprobetrace.rst
> @@ -74,7 +74,7 @@ Function arguments at kretprobe
>  -------------------------------
>  Function arguments can be accessed at kretprobe using $arg<N> fetcharg. =
This
>  is useful to record the function parameter and return value at once, and
> -trace the difference of structure fields (for debuging a function whethe=
r it
> +trace the difference of structure fields (for debugging a function wheth=
er it
>  correctly updates the given data structure or not).
>  See the :ref:`sample<fprobetrace_exit_args_sample>` in fprobe event for =
how
>  it works.

LGTM, thanks!

Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>

--=20
An old man doll... just what I always wanted! - Clara

--+qpWXA4C62hzXlBX
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQSSYQ6Cy7oyFNCHrUH2uYlJVVFOowUCZjLgoAAKCRD2uYlJVVFO
owHbAP9QPvQUjv50nrdmOPTbYojD5JzZT+xPeihn8CgadhePkwD/eExr1FkI5Di9
hrmTqwY12CpSjjyeFpuelUeEKpw5LQg=
=TxGH
-----END PGP SIGNATURE-----

--+qpWXA4C62hzXlBX--