ANDROID: mm: fix build break

MIGRATE_CMA is defined only when CONFIG_CMA. Thus, we
couldn't use MIGRATE_CMA directly to build for both
!CONFIG_CMA and CONFIG_CMA.

Let's use MIGRATE_RECLAIMABLE in the case.

Bug: 218731671
Signed-off-by: Minchan Kim <minchan@google.com>
Change-Id: Idb4fc6f4ea02ab074f270ce62001182c8fff3b37
This commit is contained in:
Minchan Kim
2022-04-12 15:00:39 -07:00
parent d9e4b67784
commit 7a197aa504

View File

@@ -3356,7 +3356,7 @@ static void free_unref_page_commit(struct page *page, unsigned long pfn)
* areas back if necessary. Otherwise, we may have to free
* excessively into the page allocator
*/
if (migratetype >= MIGRATE_CMA) {
if (migratetype > MIGRATE_RECLAIMABLE) {
if (unlikely(is_migrate_isolate(migratetype))) {
free_one_page(zone, page, pfn, 0, migratetype,
FPI_NONE);