From: Maxin B John <maxin.john@gmail.com>
To: rdunlap@xenotime.net
Cc: catalin.marinas@arm.com, dbaluta@ixiacom.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: update kmemleak architecture support info
Date: Fri, 10 Jun 2011 22:09:56 +0300 [thread overview]
Message-ID: <20110610190956.GA2742@maxin> (raw)
>> 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.
> Please send an updated patch without the currently-supported list
> of architectures.
Please find the updated patch below:
Signed-off-by: Maxin B. John <maxin.john@gmail.com>
---
diff --git a/Documentation/kmemleak.txt b/Documentation/kmemleak.txt
index 090e6ee..51063e6 100644
--- a/Documentation/kmemleak.txt
+++ b/Documentation/kmemleak.txt
@@ -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
-----
next reply other threads:[~2011-06-10 19:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 19:09 Maxin B John [this message]
2011-06-10 20:18 ` [PATCH] Documentation: update kmemleak architecture support info Randy Dunlap
2011-06-10 21:22 ` Catalin Marinas
-- 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-09 18:59 Maxin B John
2011-06-10 6:46 ` Daniel Baluta
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=20110610190956.GA2742@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.