aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorLibin <huawei.libin@huawei.com>2013-08-26 17:54:59 -0400
committerJiri Kosina <jkosina@suse.cz>2013-08-27 04:47:05 -0400
commitcb18c5e2ed48d9fbbe863c7d80f84d1964d883a3 (patch)
treed69c283c079a411bfffb678dd4c36a6d4e323554 /Documentation
parent6c1b06d6f6b39622b5f9899acc77b9af76ebcb92 (diff)
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>
Diffstat (limited to 'Documentation')
-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
91debugging a problem. This option is not mandatory, however, because it slows 91debugging a problem. This option is not mandatory, however, because it slows
92down the compilation process and produces a much bigger kernel image. 92down the compilation process and produces a much bigger kernel image.
93 93
94Now the kmemcheck menu should be visible (under "Kernel hacking" / "kmemcheck: 94Now the kmemcheck menu should be visible (under "Kernel hacking" / "Memory
95trap use of uninitialized memory"). Here follows a description of the 95Debugging" / "kmemcheck: trap use of uninitialized memory"). Here follows
96kmemcheck configuration variables: 96a description of the kmemcheck configuration variables:
97 97
98 o CONFIG_KMEMCHECK 98 o CONFIG_KMEMCHECK
99 99