linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, clameter@sgi.com,
	linux-mm@kvack.org
Subject: Re: [PATCH] Add maintainer for memory management
Date: Mon, 24 Jul 2006 00:11:28 -0700	[thread overview]
Message-ID: <20060724001128.6d513d20.rdunlap@xenotime.net> (raw)
In-Reply-To: <1153713707.4002.43.camel@localhost.localdomain>

On Mon, 24 Jul 2006 00:01:47 -0400 Steven Rostedt wrote:

> I recently realized that there's no listing of a memory management
> maintainer in the MAINTAINERS file. And didn't know about
> linux-mm@kvack.org before Ingo enlightened me.  So I've decided to add
> one.  Since Christoph is the first person to come in my mind as the
> proper maintainer, (and I haven't asked him if he wants this title :)
> I'll let him either add others to the list, or replace his name
> altogether.
> 
> (I also used the email that he had in slab.c)
> 
> Note: If someone else is more likely the person than Christoph, don't be
> offended that I didn't choose you.  It's just that Christoph has
> responded the most whenever I mention anything about memory. So I chose
> that as my criteria, than looking at who submits the most memory
> patches.
> 
> -- Steve
> 
> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
> 
> Index: linux-2.6.18-rc2/MAINTAINERS
> ===================================================================
> --- linux-2.6.18-rc2.orig/MAINTAINERS	2006-07-23 23:32:13.000000000 -0400
> +++ linux-2.6.18-rc2/MAINTAINERS	2006-07-23 23:34:10.000000000 -0400
> @@ -1884,6 +1884,12 @@ S:     linux-scsi@vger.kernel.org
>  W:     http://megaraid.lsilogic.com
>  S:     Maintained
>  
> +MEMORY MANAGEMENT
> +P:	Christoph Lameter
> +M:	christoph@lameter.com
> +L:	linux-mm@kvack.org
> +S:	Maintained
> +

Christoph L. is very NUMA & big-iron focused.  He also breaks
things (at least builds if not working code) a bit too often IMO.

Andrew, Nick, Peter Zijlstra, Pekka, Manfred, Hugh Dickins
are all a better choice IMO.  However, if Andrew & Linus want
to merge that one...

---
~Randy

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2006-07-24  7:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-24  4:01 Steven Rostedt
2006-07-24  7:11 ` Randy.Dunlap [this message]
2006-07-24 11:56   ` Steven Rostedt
2006-07-24 12:13 ` Andi Kleen
2006-07-24 12:31   ` Steven Rostedt
2006-07-24 16:28     ` Christoph Lameter
2006-07-24 16:40       ` Dave McCracken
2006-07-24 17:42       ` Steven Rostedt
2006-07-24 17:12     ` Andrew Morton
2006-07-24 14:03 ` Peter Zijlstra
2006-07-24 14:25   ` Steven Rostedt
2006-07-24 14:32   ` [PATCH] Add linux-mm mailing list for memory management in MAINTAINERS file Steven Rostedt
2006-07-24 14:56     ` Jesper Juhl
2006-07-24 16:07     ` Dave Jones
2006-07-24 16:25       ` [PATCH V2] " Steven Rostedt

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=20060724001128.6d513d20.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rostedt@goodmis.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