linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Minchan Kim <minchan@kernel.org>
To: akpm@linux-foundation.org
Cc: mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	linux-next@vger.kernel.org,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Andrea Arcangeli <aarcange@redhat.com>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: mmotm 2012-06-21-16-20 uploaded
Date: Fri, 22 Jun 2012 16:14:07 +0900	[thread overview]
Message-ID: <4FE41B3F.6090106@kernel.org> (raw)
In-Reply-To: <20120621232149.F0286A026A@akpm.mtv.corp.google.com>

Hi Andrew,

On 06/22/2012 08:21 AM, akpm@linux-foundation.org wrote:

> The mm-of-the-moment snapshot 2012-06-21-16-20 has been uploaded to
> 
>    http://www.ozlabs.org/~akpm/mmotm/
> 
> It contains the following patches against 3.5-rc3:
> (patches marked "*" will be included in linux-next)
> 
>   origin.patch
> * selinux-fix-something.patch

< snip>

> * mm-compaction-handle-incorrect-migrate_unmovable-type-pageblocks.patch
> * mm-compaction-handle-incorrect-migrate_unmovable-type-pageblocks-fix.patch


Above two patch should be dropped. It has a bug.
Ref: https://lkml.org/lkml/2012/6/13/529

I sent bug fix patch.
1. https://lkml.org/lkml/2012/6/13/568

And then, clean up patch.
2. https://lkml.org/lkml/2012/6/13/570

Bartlomiej rebased his patch on above two patches.

3. https://lkml.org/lkml/2012/6/14/361

I hope I am not too late.

-- 
Kind regards,
Minchan Kim

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

  parent reply	other threads:[~2012-06-22  7:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21 23:21 mmotm 2012-06-21-16-20 uploaded akpm
2012-06-21 23:34 ` Andrew Morton
2012-06-22  7:14 ` Minchan Kim [this message]
2012-06-22  8:14 ` viresh kumar
2012-06-22  9:23 ` Michal Hocko

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=4FE41B3F.6090106@kernel.org \
    --to=minchan@kernel.org \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mm-commits@vger.kernel.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).