[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4DF1BDB4.20602@ixiacom.com>
Date: Fri, 10 Jun 2011 09:46:12 +0300
From: Daniel Baluta <dbaluta@...acom.com>
To: Maxin B John <maxin.john@...il.com>
CC: "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"catalin.marinas@....com" <catalin.marinas@....com>,
"rdunlap@...otime.net" <rdunlap@...otime.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Documentation: update kmemleak architecture support info
On 06/09/2011 09:59 PM, Maxin B John wrote:
> Kmemleak now supports s390 and mips too.
>
> Signed-off-by: Maxin B. John<maxin.john@...il.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
> -----
Hello,
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.
thanks,
Daniel.
--
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