linux-kernel - Re: [PATCH] Add maintainer for memory management

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 24 Jul 2006 07:56:33 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	"Randy.Dunlap" <rdunlap@...otime.net>
Cc:	linux-kernel@...r.kernel.org, akpm@...l.org, clameter@....com,
	linux-mm@...ck.org
Subject: Re: [PATCH] Add maintainer for memory management

On Mon, 2006-07-24 at 00:11 -0700, Randy.Dunlap wrote:

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

Like I said, the criteria was who responded the most. I actually don't
keep track of the mm work and someone else is probably better at
deciding this. But since it doesn't exist _at_all_ in MAINTAINERS I
figured that if I post this, it will soon be added.

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

Even if Christoph is not chosen, please do add a MEMORY MANAGEMENT in
the MAINTAINERS.  I don't want to keep looking back in my email logs to
remember what that mm email list was called again.

Also, I would like to see linux-arch mentioned in the MAINTAINERS file
since before I new about it, I just emailed every arch maintainer that I
could find in the list separately, when making a change that all archs
needed.

-- Steve

-
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/