Documentation: update kmemleak architecture support info
Quoted 2 lines
Quoted 2 lines
I think Daniel's suggestion is better, we don't have to worry about changing the documentation every time we add a new architecture.
I agree with that.
Quoted 2 lines
Please send an updated patch without the currently-supported list of architectures.
Please find the updated patch below:
---
Documentation/kmemleak.txt +3 -1
@@ -11,7 +11,9 @@ with the difference that the orphan objects are not freed but only reported via /sys/kernel/debug/kmemleak. A similar method is used by the Valgrind tool (memcheck --leak-check) to detect the memory leaks in user-space applications. -Kmemleak is supported on x86, arm, powerpc, sparc, sh, microblaze and tile. + +Please check DEBUG_KMEMLEAK dependencies in lib/Kconfig.debug for supported +architectures. Usage -----
Randy Dunlap
AppliedQuoted 9 lines · On Fri, 10 Jun 2011 22:09:56 +0300 Maxin B John wrote:
Quoted 2 lines
Quoted 2 lines
I think Daniel's suggestion is better, we don't have to worry about changing the documentation every time we add a new architecture.
I agree with that.
Quoted 2 lines
Please send an updated patch without the currently-supported list of architectures.
Please find the updated patch below:
Signed-off-by Maxin B. John <[email protected]>
Applied, thanks.
Quoted 8 lines
---
Documentation/kmemleak.txt +0
-0@@ -11,7 +11,9 @@ with the difference that the orphan objects are not freed but only reported via /sys/kernel/debug/kmemleak. A similar method is used by the Valgrind tool (memcheck --leak-check) to detect the memory leaks in
Documentation/kmemleak.txt with the difference that the orphan objects are not freed but only
Quoted 10 lines
Documentation/kmemleak.txt +3
-2user-space applications. -Kmemleak is supported on x86, arm, powerpc, sparc, sh, microblaze and tile. + +Please check DEBUG_KMEMLEAK dependencies in lib/Kconfig.debug for supported +architectures. Usage ----- --
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
Quoted 5 lines · Randy Dunlap
Quoted 4 lines · On Fri, 10 Jun 2011 22:09:56 +0300 Maxin B John wrote:
Quoted 2 lines
Quoted 2 lines
I think Daniel's suggestion is better, we don't have to worry about changing the documentation every time we add a new architecture.
I agree with that.
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
Please send an updated patch without the currently-supported list of architectures.
Please find the updated patch below:
Signed-off-by Maxin B. John <[email protected]>Applied, thanks.
Thanks.
Signature · 1 line
Catalin