From: Steven Rostedt <rostedt@goodmis.org>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Christoph Lameter <clameter@sgi.com>,
linux-mm@kvack.org
Subject: Re: [PATCH] Add maintainer for memory management
Date: Mon, 24 Jul 2006 10:25:08 -0400 [thread overview]
Message-ID: <1153751108.4002.104.camel@localhost.localdomain> (raw)
In-Reply-To: <1153749795.23798.19.camel@lappy>
On Mon, 2006-07-24 at 16:03 +0200, Peter Zijlstra wrote:
> Hi Steven,
>
> The way I understand the maintainership of the memory management code is
> as follows: there is explicitly no maintainer listed. This code is so
> sensitive and has interactions with so many other sub-systems that it
> would not be doable to look at it from all possible angles by only one
> person.
>
> As it stands its more a group of people headed by Linus, Andrew and
> Hugh.
>
Thanks Peter for the explanation.
So, I'll send another patch to just add the linux-mm mailing list, since
that should have no qualms about it.
Thanks,
-- Steve
next prev parent reply other threads:[~2006-07-24 14:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-24 4:01 [PATCH] Add maintainer for memory management Steven Rostedt
2006-07-24 7:11 ` Randy.Dunlap
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 14:03 ` Peter Zijlstra
2006-07-24 14:25 ` Steven Rostedt [this message]
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=1153751108.4002.104.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).