summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLibin <huawei.libin@huawei.com>2013-08-26 14:54:59 -0700
committerJiri Kosina <jkosina@suse.cz>2013-08-27 10:47:05 +0200
commitcb18c5e2ed48d9fbbe863c7d80f84d1964d883a3 (patch)
treed69c283c079a411bfffb678dd4c36a6d4e323554
parent6c1b06d6f6b39622b5f9899acc77b9af76ebcb92 (diff)
downloadlwn-cb18c5e2ed48d9fbbe863c7d80f84d1964d883a3.tar.gz
lwn-cb18c5e2ed48d9fbbe863c7d80f84d1964d883a3.zip
Documentation/kmemcheck: update kmemcheck documentation
Kmemcheck configuration menu location correction in Documentation/ kmemcheck.txt Signed-off-by: Libin <huawei.libin@huawei.com> Acked-by: Rob Landley <rob@landley.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
-rw-r--r--Documentation/kmemcheck.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/kmemcheck.txt b/Documentation/kmemcheck.txt
index c28f82895d6b..9398a501fdb9 100644
--- a/Documentation/kmemcheck.txt
+++ b/Documentation/kmemcheck.txt
@@ -91,9 +91,9 @@ information from the kmemcheck warnings, which is extremely valuable in
debugging a problem. This option is not mandatory, however, because it slows
down the compilation process and produces a much bigger kernel image.
-Now the kmemcheck menu should be visible (under "Kernel hacking" / "kmemcheck:
-trap use of uninitialized memory"). Here follows a description of the
-kmemcheck configuration variables:
+Now the kmemcheck menu should be visible (under "Kernel hacking" / "Memory
+Debugging" / "kmemcheck: trap use of uninitialized memory"). Here follows
+a description of the kmemcheck configuration variables:
o CONFIG_KMEMCHECK