]> www.infradead.org Git - users/dwmw2/linux.git/commitdiff
docs: kmemleak: adjust to config renaming
authorLukas Bulwahn <lukas.bulwahn@gmail.com>
Fri, 14 Apr 2023 06:12:41 +0000 (08:12 +0200)
committerJonathan Corbet <corbet@lwn.net>
Thu, 20 Apr 2023 23:53:38 +0000 (17:53 -0600)
Commit c87db8ca0902 ("kmemleak-test: fix kmemleak_test.c build logic")
essentially renames the config DEBUG_KMEMLEAK_TEST to SAMPLE_KMEMLEAK, but
misses to adjust the documentation.

Adjust kmemleak documentation to this config renaming.

Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
Link: https://lore.kernel.org/r/20230414061241.12754-1-lukas.bulwahn@gmail.com
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Documentation/dev-tools/kmemleak.rst

index 5483fd39ef2956d51750e6ef2bce37b96f7defc1..2cb00b53339fe9830a41867becc9beb4650f216a 100644 (file)
@@ -227,7 +227,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
+module, a module that deliberately leaks memory. Set CONFIG_SAMPLE_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::