From: kernel test robot <lkp@intel.com>
To: Michal Clapinski <mclapinski@google.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
David Hildenbrand <david@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [akpm-mm:mm-new 424/425] mm/page_alloc.c:557:17: error: use of undeclared identifier 'MIGRATE_CMA'; did you mean 'MIGRATE_SYNC'?
Date: Wed, 18 Mar 2026 07:14:24 +0800 [thread overview]
Message-ID: <202603180711.mqOPviIG-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-new
head: c31e58126afa2665dc5b7f78c60e5fb25218d7e5
commit: 1e1dab36a7f3e06700a97696f62e7691ce4ea85a [424/425] kho: fix deferred init of kho scratch
config: x86_64-allnoconfig (https://download.01.org/0day-ci/archive/20260318/202603180711.mqOPviIG-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260318/202603180711.mqOPviIG-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202603180711.mqOPviIG-lkp@intel.com/
All errors (new ones prefixed by >>):
>> mm/page_alloc.c:557:17: error: use of undeclared identifier 'MIGRATE_CMA'; did you mean 'MIGRATE_SYNC'?
557 | migratetype = MIGRATE_CMA;
| ^~~~~~~~~~~
| MIGRATE_SYNC
include/linux/migrate_mode.h:14:2: note: 'MIGRATE_SYNC' declared here
14 | MIGRATE_SYNC,
| ^
mm/page_alloc.c:557:17: warning: implicit conversion from enumeration type 'enum migrate_mode' to different enumeration type 'enum migratetype' [-Wenum-conversion]
557 | migratetype = MIGRATE_CMA;
| ~ ^~~~~~~~~~~
1 warning and 1 error generated.
vim +557 mm/page_alloc.c
542
543 void __meminit init_pageblock_migratetype(struct page *page,
544 enum migratetype migratetype,
545 bool isolate)
546 {
547 unsigned long flags;
548
549 if (unlikely(page_group_by_mobility_disabled &&
550 migratetype < MIGRATE_PCPTYPES))
551 migratetype = MIGRATE_UNMOVABLE;
552
553 /*
554 * Mark KHO scratch as CMA so no unmovable allocations are made there.
555 */
556 if (unlikely(kho_scratch_overlap(page_to_phys(page), PAGE_SIZE)))
> 557 migratetype = MIGRATE_CMA;
558
559 flags = migratetype;
560
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-17 23:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202603180711.mqOPviIG-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=mclapinski@google.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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