[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110610070937.GA2802@maxin>
Date: Fri, 10 Jun 2011 10:09:37 +0300
From: Maxin B John <maxin.john@...il.com>
To: dbaluta@...acom.com
Cc: nux-doc@...r.kernel.org, catalin.marinas@....com,
rdunlap@...otime.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Documentation: update kmemleak architecture support
info
> 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@...il.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
-----
--
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