docs:dev-tools: Fix typo in Documentation/dev-tools
Subsystems (5)
PATCH 1/1 docs:dev-tools: Fix typo in Documentation/dev-tools
This patch fixes some spelling typos found inDocumentation/dev-tools.
Signed-off-by Masanari Iida <[email protected]>
--- 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(-)
Documentation/dev-tools/kasan.rst +2 -2
@@ -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.
Documentation/dev-tools/kcov.rst +1 -1
@@ -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
Documentation/dev-tools/kmemleak.rst +1 -1
@@ -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
Signature · 1 line
2.28.0.497.g54e85e7af1ac
Quoted 9 lines · Masanari Iida
This patch fixes some spelling typos found in
Documentation/dev-tools.Signed-off-by Masanari Iida <[email protected]>--- 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 <[email protected]>
Thanks.
Signature · 1 line
~Randy
Quoted 49 lines · Masanari Iida
This patch fixes some spelling typos found in
Documentation/dev-tools.Signed-off-by Masanari Iida <[email protected]>--- 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(-)Documentation/dev-tools/kasan.rst +2
-2@@ -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.Documentation/dev-tools/kcov.rst +1
-1@@ -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 coverageDocumentation/dev-tools/kmemleak.rst +0
-0
Documentation/dev-tools/kmemleak.rst Testing with kmemleak-test · line 235
Quoted 8 lines
Documentation/dev-tools/kmemleak.rst +1
-1@@ -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 <[email protected]>