From: David Hildenbrand <david@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: virtualization@lists.linux-foundation.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <bhe@redhat.com>, Jason Wang <jasowang@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Michal Hocko <mhocko@suse.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
Mike Rapoport <rppt@kernel.org>,
Mike Rapoport <rppt@linux.ibm.com>,
Pankaj Gupta <pankaj.gupta.linux@gmail.com>,
Qian Cai <cai@lca.pw>
Subject: Re: [PATCH v5 0/6] mm / virtio-mem: support ZONE_MOVABLE
Date: Fri, 21 Aug 2020 10:31:28 +0200 [thread overview]
Message-ID: <552a2a55-6082-d286-1cd4-7f7e368eebb4@redhat.com> (raw)
In-Reply-To: <20200816125333.7434-1-david@redhat.com>
On 16.08.20 14:53, David Hildenbrand wrote:
> For 5.10. Patch #1-#4,#6 have RBs or ACKs, patch #5 is virtio-mem stuff
> maintained by me. This should go via the -mm tree.
>
@Andrew, can we give this a churn if there are no further comments? Thanks!
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2020-08-21 8:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 12:53 David Hildenbrand
2020-08-16 12:53 ` [PATCH v5 1/6] mm/page_alloc: tweak comments in has_unmovable_pages() David Hildenbrand
2020-08-16 12:53 ` [PATCH v5 2/6] mm/page_isolation: exit early when pageblock is isolated in set_migratetype_isolate() David Hildenbrand
2020-08-16 12:53 ` [PATCH v5 3/6] mm/page_isolation: drop WARN_ON_ONCE() " David Hildenbrand
2020-08-16 12:53 ` [PATCH v5 4/6] mm/page_isolation: cleanup set_migratetype_isolate() David Hildenbrand
2020-08-16 12:53 ` [PATCH v5 5/6] virtio-mem: don't special-case ZONE_MOVABLE David Hildenbrand
2020-08-16 12:53 ` [PATCH v5 6/6] mm: document semantics of ZONE_MOVABLE David Hildenbrand
2020-08-21 8:31 ` David Hildenbrand [this message]
2020-08-21 8:45 ` [PATCH v5 0/6] mm / virtio-mem: support ZONE_MOVABLE David Hildenbrand
2020-08-21 20:55 ` Andrew Morton
2020-09-08 10:43 ` David Hildenbrand
2020-08-21 8:46 ` Baoquan He
2020-08-21 8:48 ` David Hildenbrand
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=552a2a55-6082-d286-1cd4-7f7e368eebb4@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=cai@lca.pw \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=mst@redhat.com \
--cc=pankaj.gupta.linux@gmail.com \
--cc=rppt@kernel.org \
--cc=rppt@linux.ibm.com \
--cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox