From: Catalin Marinas <catalin.marinas@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 2.6.19 10/10] Update the MAINTAINERS file for kmemleak
Date: Thu, 30 Nov 2006 23:01:58 +0000 [thread overview]
Message-ID: <20061130230157.5469.37895.stgit@localhost.localdomain> (raw)
In-Reply-To: <20061130225219.5469.2453.stgit@localhost.localdomain>
Signed-off-by: Catalin Marinas <catalin.marinas@gmail.com>
---
MAINTAINERS | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index e182992..995486d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1722,6 +1722,12 @@ L: kernel-janitors@lists.osdl.org
W: http://www.kerneljanitors.org/
S: Maintained
+KERNEL MEMORY LEAK DETECTOR
+P: Catalin Marinas
+M: catalin.marinas@gmail.com
+W: http://www.procode.org/kmemleak/
+S: Maintained
+
KERNEL NFSD
P: Neil Brown
M: neilb@cse.unsw.edu.au
prev parent reply other threads:[~2006-11-30 23:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 22:59 [PATCH 2.6.19 00/10] Kernel memory leak detector 0.12 Catalin Marinas
2006-11-30 22:59 ` [PATCH 2.6.19 01/10] Base support for kmemleak Catalin Marinas
2006-11-30 23:00 ` [PATCH 2.6.19 02/10] Kmemleak documentation Catalin Marinas
2006-11-30 23:00 ` [PATCH 2.6.19 03/10] Add the memory allocation/freeing hooks for kmemleak Catalin Marinas
2006-11-30 23:00 ` [PATCH 2.6.19 04/10] Modules support " Catalin Marinas
2006-11-30 23:00 ` [PATCH 2.6.19 05/10] Add kmemleak support for i386 Catalin Marinas
2006-11-30 23:01 ` [PATCH 2.6.19 06/10] Add kmemleak support for ARM Catalin Marinas
2006-11-30 23:01 ` [PATCH 2.6.19 07/10] Remove some of the kmemleak false positives Catalin Marinas
2006-11-30 23:01 ` [PATCH 2.6.19 08/10] Keep the __init functions after initialization Catalin Marinas
2006-11-30 23:01 ` [PATCH 2.6.19 09/10] Simple testing for kmemleak Catalin Marinas
2006-11-30 23:01 ` Catalin Marinas [this message]
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=20061130230157.5469.37895.stgit@localhost.localdomain \
--to=catalin.marinas@gmail.com \
--cc=linux-kernel@vger.kernel.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