[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200810192118.34a33d64e357ce5dd6f7614d@linux-foundation.org>
Date: Mon, 10 Aug 2020 19:21:18 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: David Hildenbrand <david@...hat.com>
Cc: linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org, linux-mm@...ck.org,
Baoquan He <bhe@...hat.com>, Jason Wang <jasowang@...hat.com>,
"Michael S. Tsirkin" <mst@...hat.com>,
Michal Hocko <mhocko@...e.com>,
Mike Kravetz <mike.kravetz@...cle.com>,
Mike Rapoport <rppt@...nel.org>,
Mike Rapoport <rppt@...ux.ibm.com>,
Pankaj Gupta <pankaj.gupta.linux@...il.com>,
Qian Cai <cai@....pw>
Subject: Re: [PATCH v4 0/6] mm / virtio-mem: support ZONE_MOVABLE
On Mon, 10 Aug 2020 09:56:32 +0200 David Hildenbrand <david@...hat.com> wrote:
> On 04.08.20 21:41, David Hildenbrand wrote:
> > @Andrew can we give this a churn and consider it for v5.9 in case there
> > are no more comments?
>
> @Andrew, Ping, so I assume we'll target v5.10?
Yep, sorry. Merging a significant patch series during the merge
window(!) would be quite extraordinary and I don't think that anything
in this patchset justifies such an action?
Powered by blists - more mailing lists