diff options
author | Libin <huawei.libin@huawei.com> | 2013-08-26 17:54:59 -0400 |
---|---|---|
committer | Jiri Kosina <jkosina@suse.cz> | 2013-08-27 04:47:05 -0400 |
commit | cb18c5e2ed48d9fbbe863c7d80f84d1964d883a3 (patch) | |
tree | d69c283c079a411bfffb678dd4c36a6d4e323554 | |
parent | 6c1b06d6f6b39622b5f9899acc77b9af76ebcb92 (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>
-rw-r--r-- | Documentation/kmemcheck.txt | 6 |
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 | |||
91 | debugging a problem. This option is not mandatory, however, because it slows | 91 | debugging a problem. This option is not mandatory, however, because it slows |
92 | down the compilation process and produces a much bigger kernel image. | 92 | down the compilation process and produces a much bigger kernel image. |
93 | 93 | ||
94 | Now the kmemcheck menu should be visible (under "Kernel hacking" / "kmemcheck: | 94 | Now the kmemcheck menu should be visible (under "Kernel hacking" / "Memory |
95 | trap use of uninitialized memory"). Here follows a description of the | 95 | Debugging" / "kmemcheck: trap use of uninitialized memory"). Here follows |
96 | kmemcheck configuration variables: | 96 | a description of the kmemcheck configuration variables: |
97 | 97 | ||
98 | o CONFIG_KMEMCHECK | 98 | o CONFIG_KMEMCHECK |
99 | 99 | ||