From: David Hildenbrand <david@redhat.com>
To: Zi Yan <ziy@nvidia.com>, linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Vlastimil Babka <vbabka@suse.cz>,
Mel Gorman <mgorman@techsingularity.net>,
Eric Ren <renzhengeek@gmail.com>, Mike Rapoport <rppt@kernel.org>,
Oscar Salvador <osalvador@suse.de>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Mike Rapoport <rppt@linux.ibm.com>
Subject: Re: [PATCH v7 1/5] mm: page_isolation: move has_unmovable_pages() to mm/page_isolation.c
Date: Mon, 14 Mar 2022 18:03:58 +0100 [thread overview]
Message-ID: <753f3cca-6862-a6b9-05a1-0b0fcc4565b8@redhat.com> (raw)
In-Reply-To: <20220311183656.1911811-2-zi.yan@sent.com>
On 11.03.22 19:36, Zi Yan wrote:
> From: Zi Yan <ziy@nvidia.com>
>
> has_unmovable_pages() is only used in mm/page_isolation.c. Move it from
> mm/page_alloc.c and make it static.
>
> Signed-off-by: Zi Yan <ziy@nvidia.com>
> Reviewed-by: Oscar Salvador <osalvador@suse.de>
> Reviewed-by: Mike Rapoport <rppt@linux.ibm.com>
Acked-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-03-14 17:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 18:36 [PATCH v7 0/5] Use pageblock_order for cma and alloc_contig_range alignment Zi Yan
2022-03-11 18:36 ` [PATCH v7 1/5] mm: page_isolation: move has_unmovable_pages() to mm/page_isolation.c Zi Yan
2022-03-14 17:03 ` David Hildenbrand [this message]
2022-03-11 18:36 ` [PATCH v7 2/5] mm: page_isolation: check specified range for unmovable pages Zi Yan
2022-03-14 17:13 ` David Hildenbrand
2022-03-14 17:58 ` Zi Yan
2022-03-11 18:36 ` [PATCH v7 3/5] mm: make alloc_contig_range work at pageblock granularity Zi Yan
2022-03-11 18:36 ` [PATCH v7 4/5] mm: cma: use pageblock_order as the single alignment Zi Yan
2022-03-11 18:36 ` [PATCH v7 5/5] drivers: virtio_mem: use pageblock size as the minimum virtio_mem size Zi Yan
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=753f3cca-6862-a6b9-05a1-0b0fcc4565b8@redhat.com \
--to=david@redhat.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=osalvador@suse.de \
--cc=renzhengeek@gmail.com \
--cc=rppt@kernel.org \
--cc=rppt@linux.ibm.com \
--cc=vbabka@suse.cz \
--cc=virtualization@lists.linux-foundation.org \
--cc=ziy@nvidia.com \
/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