public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Baluta <dbaluta@ixiacom.com>
To: Maxin B John <maxin.john@gmail.com>
Cc: "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
	"rdunlap@xenotime.net" <rdunlap@xenotime.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation: update kmemleak architecture support info
Date: Fri, 10 Jun 2011 09:46:12 +0300	[thread overview]
Message-ID: <4DF1BDB4.20602@ixiacom.com> (raw)
In-Reply-To: <20110609185957.GA3250@maxin>

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@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
>   -----
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.

  reply	other threads:[~2011-06-10  6:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09 18:59 [PATCH] Documentation: update kmemleak architecture support info Maxin B John
2011-06-10  6:46 ` Daniel Baluta [this message]
  -- 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=4DF1BDB4.20602@ixiacom.com \
    --to=dbaluta@ixiacom.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxin.john@gmail.com \
    --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