aboutsummaryrefslogtreecommitdiff
path: root/Documentation/dev-tools/kmemleak.rst
diff options
context:
space:
mode:
authorJonathan Neuschäfer2020-03-03 20:42:15 +0100
committerJonathan Corbet2020-03-10 11:32:12 -0600
commit6480e449646cdbfce239cec0b6cdc66b9617b802 (patch)
treec13f0e2bb813f8b0357df22dc64d09a6120ead59 /Documentation/dev-tools/kmemleak.rst
parentb53366a979f74ecdd893aa237e329366e3f028f8 (diff)
docs: dev-tools: kmemleak: Update list of architectures
* Don't list powerpc twice (once as ppc) * Drop tile, which has been removed from the source tree * Mention arm64, nds32, arc, and xtensa Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net> Link: https://lore.kernel.org/r/20200303194215.23756-1-j.neuschaefer@gmx.net Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/dev-tools/kmemleak.rst')
-rw-r--r--Documentation/dev-tools/kmemleak.rst3
1 files changed, 2 insertions, 1 deletions
diff --git a/Documentation/dev-tools/kmemleak.rst b/Documentation/dev-tools/kmemleak.rst
index 3a289e8a1d12..fce262883984 100644
--- a/Documentation/dev-tools/kmemleak.rst
+++ b/Documentation/dev-tools/kmemleak.rst
@@ -8,7 +8,8 @@ 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, ppc, mips, s390 and tile.
+Kmemleak is supported on x86, arm, arm64, powerpc, sparc, sh, microblaze, mips,
+s390, nds32, arc and xtensa.
Usage
-----