From: Roman Gushchin <guro@fb.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>
Cc: Michal Hocko <mhocko@kernel.org>, Tejun Heo <tj@kernel.org>,
linux-mm@kvack.org, kernel-team@fb.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] memory.min fixes/refinements
Date: Mon, 11 Jun 2018 16:09:58 -0700 [thread overview]
Message-ID: <20180611230955.GA3202@castle> (raw)
In-Reply-To: <20180611153621.aefcf17a4d4d0b939eb35f28@linux-foundation.org>
On Mon, Jun 11, 2018 at 03:36:21PM -0700, Andrew Morton wrote:
> On Mon, 11 Jun 2018 10:54:15 -0700 Roman Gushchin <guro@fb.com> wrote:
>
> > Hi, Andrew!
> >
> > Please, find an updated version of memory.min refinements/fixes
> > in this patchset. It's against linus tree.
> > Please, merge these patches into 4.18.
> >
> > ...
> >
> > mm: fix null pointer dereference in mem_cgroup_protected
> > mm, memcg: propagate memory effective protection on setting
> > memory.min/low
> > mm, memcg: don't skip memory guarantee calculations
>
> Has nobody reviewed or acked #2 and #3?
>
Looks so...
You took them very fast into the mm tree last time, so probably nobody
did give it too much attention.
Johannes, can you, please, take a look?
Thanks!
WARNING: multiple messages have this Message-ID (diff)
From: Roman Gushchin <guro@fb.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>, Tejun Heo <tj@kernel.org>,
<linux-mm@kvack.org>, <kernel-team@fb.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] memory.min fixes/refinements
Date: Mon, 11 Jun 2018 16:09:58 -0700 [thread overview]
Message-ID: <20180611230955.GA3202@castle> (raw)
In-Reply-To: <20180611153621.aefcf17a4d4d0b939eb35f28@linux-foundation.org>
On Mon, Jun 11, 2018 at 03:36:21PM -0700, Andrew Morton wrote:
> On Mon, 11 Jun 2018 10:54:15 -0700 Roman Gushchin <guro@fb.com> wrote:
>
> > Hi, Andrew!
> >
> > Please, find an updated version of memory.min refinements/fixes
> > in this patchset. It's against linus tree.
> > Please, merge these patches into 4.18.
> >
> > ...
> >
> > mm: fix null pointer dereference in mem_cgroup_protected
> > mm, memcg: propagate memory effective protection on setting
> > memory.min/low
> > mm, memcg: don't skip memory guarantee calculations
>
> Has nobody reviewed or acked #2 and #3?
>
Looks so...
You took them very fast into the mm tree last time, so probably nobody
did give it too much attention.
Johannes, can you, please, take a look?
Thanks!
next prev parent reply other threads:[~2018-06-11 23:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 17:54 [PATCH v2 0/3] memory.min fixes/refinements Roman Gushchin
2018-06-11 17:54 ` Roman Gushchin
2018-06-11 17:54 ` [PATCH v2 1/3] mm: fix null pointer dereference in mem_cgroup_protected Roman Gushchin
2018-06-11 17:54 ` Roman Gushchin
2018-06-11 17:54 ` [PATCH v2 2/3] mm, memcg: propagate memory effective protection on setting memory.min/low Roman Gushchin
2018-06-11 17:54 ` Roman Gushchin
2018-06-12 15:52 ` Johannes Weiner
2018-06-12 17:24 ` Roman Gushchin
2018-06-12 17:24 ` Roman Gushchin
2018-06-11 17:54 ` [PATCH v2 3/3] mm, memcg: don't skip memory guarantee calculations Roman Gushchin
2018-06-11 17:54 ` Roman Gushchin
2018-06-11 22:36 ` [PATCH v2 0/3] memory.min fixes/refinements Andrew Morton
2018-06-11 22:36 ` Andrew Morton
2018-06-11 23:09 ` Roman Gushchin [this message]
2018-06-11 23:09 ` Roman Gushchin
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=20180611230955.GA3202@castle \
--to=guro@fb.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=tj@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 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.