mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: torvalds <torvalds@linux-foundation.org>,
	"Maxin B. John" <maxin.john@gmail.com>
Subject: [PATCH 2/4] Documentation: update kmemleak supported archs
Date: Wed, 15 Jun 2011 12:58:29 -0700	[thread overview]
Message-ID: <20110615125829.c66701db.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110615125709.ffc06d02.randy.dunlap@oracle.com>

From: Maxin B. John <maxin.john@gmail.com>

Instead of listing the architectures that are supported by
kmemleak in Documentation/kmemleak.txt, just refer people to
the list of supported architecutures in lib/Kconfig.debug so
that Documentation/kmemleak.txt does not need more updates
for this.

Signed-off-by: Maxin B. John <maxin.john@gmail.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
---
 Documentation/kmemleak.txt |    4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

--- lnx-30-rc2.orig/Documentation/kmemleak.txt
+++ lnx-30-rc2/Documentation/kmemleak.txt
@@ -11,7 +11,9 @@ with the difference that the orphan obje
 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
 -----

  reply	other threads:[~2011-06-15 20:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-15 19:57 [PATCH 1/4] Documentation: update printk-formats.txt Randy Dunlap
2011-06-15 19:58 ` Randy Dunlap [this message]
2011-06-15 19:59 ` [PATCH 3/4] Documentation: update cgroupfs mount point Randy Dunlap
2011-06-15 20:00 ` [PATCH 4/4] Documentation: fix cgroup typos and formatting Randy Dunlap

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=20110615125829.c66701db.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxin.john@gmail.com \
    --cc=torvalds@linux-foundation.org \
    /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

Powered by JetHome