All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxin B John <maxin.john@gmail.com>
To: linux-doc@vger.kernel.org
Cc: catalin.marinas@arm.com, rdunlap@xenotime.net,
	dbaluta@ixiacom.com, linux-kernel@vger.kernel.org
Subject: [PATCH] Documentation: update kmemleak architecture support info
Date: Thu, 9 Jun 2011 21:59:58 +0300	[thread overview]
Message-ID: <20110609185957.GA3250@maxin> (raw)

Kmemleak now supports s390 and mips too.

Signed-off-by: Maxin B. John <maxin.john@gmail.com>
---
diff --git a/Documentation/kmemleak.txt b/Documentation/kmemleak.txt
index 090e6ee..82833ff 100644
--- a/Documentation/kmemleak.txt
+++ b/Documentation/kmemleak.txt
@@ -11,7 +11,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 and tile.
+Kmemleak is supported on x86, arm, powerpc, sparc, sh, microblaze, tile,
+s390 and mips.
 
 Usage
 -----

             reply	other threads:[~2011-06-09 19:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09 18:59 Maxin B John [this message]
2011-06-10  6:46 ` [PATCH] Documentation: update kmemleak architecture support info Daniel Baluta
  -- strict thread matches above, loose matches on Subject: below --
2011-06-10  7:09 Maxin B John
2011-06-10  7:18 ` Daniel Baluta
2011-06-10 14:55   ` Catalin Marinas
2011-06-10 17:55     ` Randy Dunlap
2011-06-10 19:09 Maxin B John
2011-06-10 20:18 ` Randy Dunlap
2011-06-10 21:22   ` Catalin Marinas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110609185957.GA3250@maxin \
    --to=maxin.john@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=dbaluta@ixiacom.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.