[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190822162709.fa100ba6c58e15ea35670616@linux-foundation.org>
Date: Thu, 22 Aug 2019 16:27:09 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Roman Gushchin <guro@...com>
Cc: <linux-mm@...ck.org>, Michal Hocko <mhocko@...nel.org>,
Johannes Weiner <hannes@...xchg.org>,
<linux-kernel@...r.kernel.org>, <kernel-team@...com>
Subject: Re: [PATCH v3 0/3] vmstats/vmevents flushing
On Mon, 19 Aug 2019 16:00:51 -0700 Roman Gushchin <guro@...com> wrote:
> v3:
> 1) rearranged patches [2/3] and [3/3] to make [1/2] and [2/2] suitable
> for stable backporting
>
> v2:
> 1) fixed !CONFIG_MEMCG_KMEM build by moving memcg_flush_percpu_vmstats()
> and memcg_flush_percpu_vmevents() out of CONFIG_MEMCG_KMEM
> 2) merged add-comments-to-slab-enums-definition patch in
>
> Thanks!
>
> Roman Gushchin (3):
> mm: memcontrol: flush percpu vmstats before releasing memcg
> mm: memcontrol: flush percpu vmevents before releasing memcg
> mm: memcontrol: flush percpu slab vmstats on kmem offlining
>
Can you please explain why the first two patches were cc:stable but not
the third?
Powered by blists - more mailing lists