[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20110615125829.c66701db.randy.dunlap@oracle.com>
Date: Wed, 15 Jun 2011 12:58:29 -0700
From: Randy Dunlap <randy.dunlap@...cle.com>
To: lkml <linux-kernel@...r.kernel.org>
Cc: torvalds <torvalds@...ux-foundation.org>,
"Maxin B. John" <maxin.john@...il.com>
Subject: [PATCH 2/4] Documentation: update kmemleak supported archs
From: Maxin B. John <maxin.john@...il.com>
Instead of listing the architectures that are supported by
kmemleak in Documentation/kmemleak.txt, just refer people to
the list of supported architecutures in lib/Kconfig.debug so
that Documentation/kmemleak.txt does not need more updates
for this.
Signed-off-by: Maxin B. John <maxin.john@...il.com>
Signed-off-by: Randy Dunlap <randy.dunlap@...cle.com>
---
---
Documentation/kmemleak.txt | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
--- lnx-30-rc2.orig/Documentation/kmemleak.txt
+++ lnx-30-rc2/Documentation/kmemleak.txt
@@ -11,7 +11,9 @@ with the difference that the orphan obje
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
-----
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists