From: Konstantin Khlebnikov <koct9i@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michal Hocko <mhocko@suse.cz>, linux-mm <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Rik van Riel <riel@redhat.com>, Tim Hartrick <tim@edgecast.com>,
Daniel Forrest <dan.forrest@ssec.wisc.edu>,
Hugh Dickins <hughd@google.com>,
Michel Lespinasse <walken@google.com>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH v3] mm: prevent endless growth of anon_vma hierarchy
Date: Wed, 17 Dec 2014 13:04:25 +0400 [thread overview]
Message-ID: <CALYGNiNSA1faTB_9Ngdrsv8xS7einysdMmmVeX=T-aX_RJLobg@mail.gmail.com> (raw)
In-Reply-To: <20141216155028.6a500d7a79eab815dbeb950e@linux-foundation.org>
On Wed, Dec 17, 2014 at 2:50 AM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Tue, 16 Dec 2014 11:42:18 +0100 Michal Hocko <mhocko@suse.cz> wrote:
>
>> What happened to this patch? I do not see it merged for 3.19 and
>> nor in the current mmotm tree (2014-12-15-17-05)
>>
>
> Awaiting v4. See Konstantin's reply to Rik's review comments.
>
> Konstantin, please ensure that the questions which Rik asked are
> answered (via code comments and changelogging) in the next version?
> Because other future readers will have the same questions.
>
Done.
Thanks for reminding.
prev parent reply other threads:[~2014-12-17 9:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 18:11 [PATCH v3] mm: prevent endless growth of anon_vma hierarchy Konstantin Khlebnikov
2014-11-26 19:30 ` Rik van Riel
2014-11-26 20:20 ` Konstantin Khlebnikov
2014-11-26 21:05 ` Daniel Forrest
2014-11-26 22:35 ` Andrew Morton
2014-11-27 9:13 ` Michal Hocko
2014-12-16 10:42 ` Michal Hocko
2014-12-16 23:50 ` Andrew Morton
2014-12-17 9:04 ` Konstantin Khlebnikov [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='CALYGNiNSA1faTB_9Ngdrsv8xS7einysdMmmVeX=T-aX_RJLobg@mail.gmail.com' \
--to=koct9i@gmail.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dan.forrest@ssec.wisc.edu \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=riel@redhat.com \
--cc=tim@edgecast.com \
--cc=vbabka@suse.cz \
--cc=walken@google.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;
as well as URLs for NNTP newsgroup(s).