All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Jian Peng <jipeng@broadcom.com>
Cc: David Daney <ddaney@caviumnetworks.com>,
	"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: patch to support topdown mmap allocation in MIPS
Date: Wed, 9 Nov 2011 17:45:20 +0000	[thread overview]
Message-ID: <20111109174520.GA3857@linux-mips.org> (raw)
In-Reply-To: <E18F441196CA634DB8E1F1C56A50A874572CCBB6B5@IRVEXCHCCR01.corp.ad.broadcom.com>

On Wed, May 25, 2011 at 10:47:04AM -0700, Jian Peng wrote:

> What else should I do to get this patch merged?

Since there *still* is confusion about the merge status of this patch:
I merged https://patchwork.linux-mips.org/patch/2389/ already for
Linux 3.0 as commit id d0be89f6c2570a63ac44ccdd12473a54243cd296.

https://patchwork.linux-mips.org/patch/2412/ is still marked as "new"
in patchwork and I'm going to drop it now.

  Ralf

  parent reply	other threads:[~2011-11-09 17:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16 21:09 patch to support topdown mmap allocation in MIPS Jian Peng
2011-05-16 23:37 ` Jian Peng
2011-05-17  0:12 ` David Daney
2011-05-17  1:06   ` Jian Peng
2011-05-17 16:49     ` David Daney
2011-05-17 19:37       ` Jian Peng
2011-05-25 17:47         ` Jian Peng
2011-05-25 17:58           ` David Daney
2011-05-25 18:06             ` Jian Peng
2011-06-13 23:43               ` Jian Peng
2011-06-14  0:21                 ` Jian Peng
2011-11-09 17:45           ` Ralf Baechle [this message]
2011-05-17  1:27   ` Kevin Cernekee
2011-05-17  4:04     ` Jian Peng
2011-05-17 15:18     ` [PATCH] MIPS: Cleanup arch_get_unmapped_area Ralf Baechle
2011-05-17 16:52     ` patch to support topdown mmap allocation in MIPS Ralf Baechle

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=20111109174520.GA3857@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=ddaney@caviumnetworks.com \
    --cc=jipeng@broadcom.com \
    --cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.