From: Maxin B John <maxin.john@gmail.com>
To: dbaluta@ixiacom.com
Cc: nux-doc@vger.kernel.org, catalin.marinas@arm.com,
rdunlap@xenotime.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: update kmemleak architecture support info
Date: Fri, 10 Jun 2011 10:09:37 +0300 [thread overview]
Message-ID: <20110610070937.GA2802@maxin> (raw)
> I am fine with this. What do you say about having
> something generic like:
>
> "Please check DEBUG_KMEMLEAK dependencies in lib/Kconfig.debug
> for supported platforms"
>
> In this way, there's no need to update kememleak.txt everytime
> when a new platform is supported.
I think it looks better. I have updated the Documentation as per your
suggestion. Please find the modified patch below:
Signed-off-by: Maxin B. John <maxin.john@gmail.com>
---
diff --git a/Documentation/kmemleak.txt b/Documentation/kmemleak.txt
index 090e6ee..0915667 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.
+Kmemleak is supported on x86, arm, powerpc, sparc, sh, microblaze, tile,
+s390 and mips.Please check DEBUG_KMEMLEAK dependencies in lib/Kconfig.debug
+for supported platforms.
Usage
-----
next reply other threads:[~2011-06-10 7:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 7:09 Maxin B John [this message]
2011-06-10 7:18 ` [PATCH] Documentation: update kmemleak architecture support info Daniel Baluta
2011-06-10 14:55 ` Catalin Marinas
2011-06-10 17:55 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2011-06-10 19:09 Maxin B John
2011-06-10 20:18 ` Randy Dunlap
2011-06-10 21:22 ` Catalin Marinas
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=20110610070937.GA2802@maxin \
--to=maxin.john@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=dbaluta@ixiacom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nux-doc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox