[PATCH linux-next] docs:dev-tools: Fix typo in Documentation/dev-tools

[PATCH linux-next] docs:dev-tools: Fix typo in Documentation/dev-tools

[Masanari Iida]

This patch fixes some spelling typos found in
Documentation/dev-tools.

Signed-off-by: Masanari Iida <standby24x7@gmail.com>
---
 Documentation/dev-tools/kasan.rst    | 4 ++--
 Documentation/dev-tools/kcov.rst     | 2 +-
 Documentation/dev-tools/kmemleak.rst | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/Documentation/dev-tools/kasan.rst b/Documentation/dev-tools/kasan.rst
index c09c9ca2ff1c..49ec0ab6cfc7 100644
--- a/Documentation/dev-tools/kasan.rst
+++ b/Documentation/dev-tools/kasan.rst
@@ -328,7 +328,7 @@ using something like insmod or modprobe. The module is called ``test_kasan``.
 ~~~~~~~~~~~~~
 
 With ``CONFIG_KUNIT`` built-in, ``CONFIG_KASAN_KUNIT_TEST`` can be built-in
-on any architecure that supports KASAN. These and any other KUnit
+on any architecture that supports KASAN. These and any other KUnit
 tests enabled will run and print the results at boot as a late-init
 call.
 
@@ -349,5 +349,5 @@ converted to KUnit. These tests can be run only as a module with
 ``CONFIG_KASAN`` built-in. The type of error expected and the
 function being run is printed before the expression expected to give
 an error. Then the error is printed, if found, and that test
-should be interpretted to pass only if the error was the one expected
+should be interpreted to pass only if the error was the one expected
 by the test.
diff --git a/Documentation/dev-tools/kcov.rst b/Documentation/dev-tools/kcov.rst
index 8548b0b04e43..d2c4c27e1702 100644
--- a/Documentation/dev-tools/kcov.rst
+++ b/Documentation/dev-tools/kcov.rst
@@ -243,7 +243,7 @@ handles as they don't belong to a particular subsystem. The bytes 4-7 are
 currently reserved and must be zero. In the future the number of bytes
 used for the subsystem or handle ids might be increased.
 
-When a particular userspace proccess collects coverage via a common
+When a particular userspace process collects coverage via a common
 handle, kcov will collect coverage for each code section that is annotated
 to use the common handle obtained as kcov_handle from the current
 task_struct. However non common handles allow to collect coverage
diff --git a/Documentation/dev-tools/kmemleak.rst b/Documentation/dev-tools/kmemleak.rst
index a41a2d238af2..1c935f41cd3a 100644
--- a/Documentation/dev-tools/kmemleak.rst
+++ b/Documentation/dev-tools/kmemleak.rst
@@ -229,7 +229,7 @@ Testing with kmemleak-test
 
 To check if you have all set up to use kmemleak, you can use the kmemleak-test
 module, a module that deliberately leaks memory. Set CONFIG_DEBUG_KMEMLEAK_TEST
-as module (it can't be used as bult-in) and boot the kernel with kmemleak
+as module (it can't be used as built-in) and boot the kernel with kmemleak
 enabled. Load the module and perform a scan with::
 
         # modprobe kmemleak-test
-- 
2.28.0.497.g54e85e7af1ac

Re: [PATCH linux-next] docs:dev-tools: Fix typo in Documentation/dev-tools

[Randy Dunlap]

On 9/17/20 6:44 AM, Masanari Iida wrote:
> This patch fixes some spelling typos found in
> Documentation/dev-tools.
> 
> Signed-off-by: Masanari Iida <standby24x7@gmail.com>
> ---
>  Documentation/dev-tools/kasan.rst    | 4 ++--
>  Documentation/dev-tools/kcov.rst     | 2 +-
>  Documentation/dev-tools/kmemleak.rst | 2 +-
>  3 files changed, 4 insertions(+), 4 deletions(-)

Acked-by: Randy Dunlap <rdunlap@infradead.org>

Thanks.

-- 
~Randy

Re: [PATCH linux-next] docs:dev-tools: Fix typo in Documentation/dev-tools

[Andrey Konovalov]

On Thu, Sep 17, 2020 at 3:44 PM Masanari Iida <standby24x7@gmail.com> wrote:
>
> This patch fixes some spelling typos found in
> Documentation/dev-tools.
>
> Signed-off-by: Masanari Iida <standby24x7@gmail.com>
> ---
>  Documentation/dev-tools/kasan.rst    | 4 ++--
>  Documentation/dev-tools/kcov.rst     | 2 +-
>  Documentation/dev-tools/kmemleak.rst | 2 +-
>  3 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/dev-tools/kasan.rst b/Documentation/dev-tools/kasan.rst
> index c09c9ca2ff1c..49ec0ab6cfc7 100644
> --- a/Documentation/dev-tools/kasan.rst
> +++ b/Documentation/dev-tools/kasan.rst
> @@ -328,7 +328,7 @@ using something like insmod or modprobe. The module is called ``test_kasan``.
>  ~~~~~~~~~~~~~
>
>  With ``CONFIG_KUNIT`` built-in, ``CONFIG_KASAN_KUNIT_TEST`` can be built-in
> -on any architecure that supports KASAN. These and any other KUnit
> +on any architecture that supports KASAN. These and any other KUnit
>  tests enabled will run and print the results at boot as a late-init
>  call.
>
> @@ -349,5 +349,5 @@ converted to KUnit. These tests can be run only as a module with
>  ``CONFIG_KASAN`` built-in. The type of error expected and the
>  function being run is printed before the expression expected to give
>  an error. Then the error is printed, if found, and that test
> -should be interpretted to pass only if the error was the one expected
> +should be interpreted to pass only if the error was the one expected
>  by the test.
> diff --git a/Documentation/dev-tools/kcov.rst b/Documentation/dev-tools/kcov.rst
> index 8548b0b04e43..d2c4c27e1702 100644
> --- a/Documentation/dev-tools/kcov.rst
> +++ b/Documentation/dev-tools/kcov.rst
> @@ -243,7 +243,7 @@ handles as they don't belong to a particular subsystem. The bytes 4-7 are
>  currently reserved and must be zero. In the future the number of bytes
>  used for the subsystem or handle ids might be increased.
>
> -When a particular userspace proccess collects coverage via a common
> +When a particular userspace process collects coverage via a common
>  handle, kcov will collect coverage for each code section that is annotated
>  to use the common handle obtained as kcov_handle from the current
>  task_struct. However non common handles allow to collect coverage
> diff --git a/Documentation/dev-tools/kmemleak.rst b/Documentation/dev-tools/kmemleak.rst
> index a41a2d238af2..1c935f41cd3a 100644
> --- a/Documentation/dev-tools/kmemleak.rst
> +++ b/Documentation/dev-tools/kmemleak.rst
> @@ -229,7 +229,7 @@ Testing with kmemleak-test
>
>  To check if you have all set up to use kmemleak, you can use the kmemleak-test
>  module, a module that deliberately leaks memory. Set CONFIG_DEBUG_KMEMLEAK_TEST
> -as module (it can't be used as bult-in) and boot the kernel with kmemleak
> +as module (it can't be used as built-in) and boot the kernel with kmemleak
>  enabled. Load the module and perform a scan with::
>
>          # modprobe kmemleak-test

Reviewed-by: Andrey Konovalov <andreyknvl@google.com>