From: Johannes Weiner <hannes@cmpxchg.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michal Hocko <mhocko@suse.cz>, linux-mm@kvack.org
Subject: Re: mm-memcontrol-rewrite-charge-api.patch and mm-memcontrol-rewrite-uncharge-api.patch
Date: Wed, 6 Aug 2014 22:26:48 -0400 [thread overview]
Message-ID: <20140807022648.GA30560@cmpxchg.org> (raw)
In-Reply-To: <20140806135914.9fca00159f6e3298c24a4ab3@linux-foundation.org>
On Wed, Aug 06, 2014 at 01:59:14PM -0700, Andrew Morton wrote:
>
> Do we feel these are ready for merging?
>
> I'll send along the consolidated patches for eyeballs.
I just went over them again, as well as over the individual fixes.
The uncharge-from-irq-context was a more fundamental fix-up, as was
getting migration from fuse splicing right, but aside from that I
think the fallout was fairly mild and seems to have settled; the last
bug fix is from two weeks ago. Given how much this series reduces the
burden memcg puts on users and maintainers, I think it should go in.
Thanks!
--
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>
next prev parent reply other threads:[~2014-08-07 2:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 20:59 mm-memcontrol-rewrite-charge-api.patch and mm-memcontrol-rewrite-uncharge-api.patch Andrew Morton
2014-08-06 21:00 ` mm: memcontrol: rewrite charge API Andrew Morton
2014-08-06 21:00 ` mm: memcontrol: rewrite uncharge API Andrew Morton
2014-08-06 21:02 ` Andrew Morton
2014-08-07 7:38 ` Michal Hocko
2014-08-07 16:25 ` Johannes Weiner
2014-08-07 22:40 ` Andrew Morton
2014-08-07 23:02 ` Johannes Weiner
2014-08-07 23:18 ` Johannes Weiner
2014-08-08 11:42 ` Michal Hocko
2014-08-07 2:26 ` Johannes Weiner [this message]
2014-08-07 7:44 ` mm-memcontrol-rewrite-charge-api.patch and mm-memcontrol-rewrite-uncharge-api.patch 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=20140807022648.GA30560@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@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 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.