From: Andrew Morton <akpm@linux-foundation.org>
To: Kevin Hilman <khilman@linaro.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-next@vger.kernel.org, vbabka@suse.cz,
Olof Johansson <olof@lixom.net>
Subject: Re: mmotm 2013-08-27-16-51 uploaded
Date: Thu, 5 Sep 2013 13:17:09 -0700 [thread overview]
Message-ID: <20130905131709.2902b944.akpm@linux-foundation.org> (raw)
In-Reply-To: <CAGa+x85d-RWYPkmTVapzcYFEzPhUU7YLJHZVGK0cGc=AudYubQ@mail.gmail.com>
On Thu, 5 Sep 2013 13:05:38 -0700 Kevin Hilman <khilman@linaro.org> wrote:
> On Tue, Aug 27, 2013 at 4:52 PM, <akpm@linux-foundation.org> wrote:
>
> > This mmotm tree contains the following patches against 3.11-rc7:
> > (patches marked "*" will be included in linux-next)
>
> [...]
>
> > * mm-munlock-manual-pte-walk-in-fast-path-instead-of-follow_page_mask.patch
>
> As has already been pointed out[1], this one introduced a new warning
> in -next (also lovingly acknowledged in the mmotm series file[2]) and
> it seems that Vlastimil has posted an updated version[3]. Any plans
> to pick up the new version for -next (or at least drop the one causing
> the new warning?)
>
yup. I'm not here at present. Next Tuesday I'll be back in the saddle
with a big scramble to address the known -mm bloopers and then do a
rather late merge for -rc1.
--
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>
prev parent reply other threads:[~2013-09-05 20:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 23:52 mmotm 2013-08-27-16-51 uploaded akpm
2013-08-28 0:50 ` Stephen Boyd
2013-08-28 1:26 ` Andrew Morton
2013-08-28 18:42 ` Stephen Boyd
2013-08-28 1:39 ` Bo Shen
2013-08-28 15:35 ` Michal Hocko
2013-09-05 20:05 ` Kevin Hilman
2013-09-05 20:17 ` 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=20130905131709.2902b944.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=khilman@linaro.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--cc=vbabka@suse.cz \
/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).