linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-mm@kvack.org
Subject: Re: what to patch
Date: Mon, 10 Mar 2008 12:55:59 -0700	[thread overview]
Message-ID: <20080310125559.796bdaaf.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080310122010.a2170c9c.randy.dunlap@oracle.com>

On Mon, 10 Mar 2008 12:20:10 -0700
Randy Dunlap <randy.dunlap@oracle.com> wrote:

> On Mon, 10 Mar 2008 12:09:02 -0700 Andrew Morton wrote:
> 
> > I get a significant-looking reject from this.  Can you please redo and
> > resend?
> > 
> > 
> > I put my current rollup (against -rc5) at
> > http://userweb.kernel.org/~akpm/dr.gz and the broken-out tree is, as always
> > at http://userweb.kernel.org/~akpm/mmotm/
> > 
> > It would be better for you to get set up for using mmotm - it is my usual
> > way of publishing the -mm queue between releases.
> 
> Speaking of what to patch, I'm looking at making a big set of
> kernel-docbook changes/fixes/additions to the mm/ subdir.
> Should I make patches to mainline or -mm (or mmotm) or what?

mmotm would be best please.

> mm/ seems to have a *lot* of patches. ;)

Actually the number of memory-management patches in -mm is much less this
time than it usually is.  Perhaps we finished it.

--
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:[~2008-03-10 19:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.1.00.0803071720460.4611@chino.kir.corp.google.com>
     [not found] ` <20080310120902.5f25b9f9.akpm@linux-foundation.org>
2008-03-10 19:20   ` Randy Dunlap
2008-03-10 19:55     ` Andrew Morton [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=20080310125559.796bdaaf.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=randy.dunlap@oracle.com \
    /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