From: Andrew Morton <akpm@osdl.org>
To: Gerrit Huizenga <gh@us.ibm.com>
Cc: mef@CS.Princeton.EDU, linux-kernel@vger.kernel.org,
riel@redhat.com, mason@suse.com, ckrm-tech@lists.sourceforge.net,
llp@CS.Princeton.EDU, acb@CS.Princeton.EDU,
mlhuang@CS.Princeton.EDU, smuir@CS.Princeton.EDU
Subject: Re: [ckrm-tech] Re: [PATCH] CKRM: 0/10 Class Based Kernel Resource Management
Date: Sun, 5 Dec 2004 22:30:14 -0800 [thread overview]
Message-ID: <20041205223014.79c9bf16.akpm@osdl.org> (raw)
In-Reply-To: <E1CaVM9-0005yy-00@w-gerrit.beaverton.ibm.com>
Gerrit Huizenga <gh@us.ibm.com> wrote:
>
> So, Andrew, can you clarify how much we need to put in your hands, how
> well tested it needs to be and how clean and current the entire set needs
> to be before this is ready for -mm testing?
Well we can toss stuff into -mm any old time really. Doing it too early
will cause rather a lot of difficulty and churn at both ends - working
against -mm can be an extra burden at times.
I'd say that it would be best to wait until the code is, in your opinion,
in a Linus-mergeable form. Then after one lkml review round and any
subsequent rework we should be in good shape.
next prev parent reply other threads:[~2004-12-06 6:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 18:44 Gerrit Huizenga
2004-11-29 20:23 ` Andrew Morton
2004-11-29 22:33 ` Gerrit Huizenga
2004-12-03 11:54 ` [ckrm-tech] " Marc E. Fiuczynski
2004-12-04 0:40 ` Andrew Morton
2004-12-04 8:33 ` Gerrit Huizenga
2004-12-06 6:30 ` Andrew Morton [this message]
2004-11-29 22:32 ` Christoph Hellwig
2004-11-29 22:51 ` Gerrit Huizenga
2004-11-30 8:55 ` Nikita Danilov
2004-11-30 2:43 ` Greg KH
2004-11-30 2:48 ` Gerrit Huizenga
2004-11-30 4:07 ` Greg KH
2004-11-30 5:59 ` Gerrit Huizenga
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=20041205223014.79c9bf16.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=acb@CS.Princeton.EDU \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=gh@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llp@CS.Princeton.EDU \
--cc=mason@suse.com \
--cc=mef@CS.Princeton.EDU \
--cc=mlhuang@CS.Princeton.EDU \
--cc=riel@redhat.com \
--cc=smuir@CS.Princeton.EDU \
/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
all inboxes | Powered by JetHome®