From: kernel test robot <lkp@intel.com>
To: "Pratyush Yadav (Google)" <pratyush@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
0day robot <lkp@intel.com>
Subject: mm/mm_init.c:2691:2: error: call to undeclared function 'kho_extend_scratch'; ISO C99 and later do not support implicit function declarations
Date: Thu, 30 Apr 2026 09:51:53 +0200 [thread overview]
Message-ID: <202604300954.lysOjEtq-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Pratyush-Yadav/kho-generalize-radix-tree-APIs/20260430-095605
head: a586b345757dd389b6a3981b387cc4b39c538fab
commit: a29db33861c799b78a6469b22301aace345ad455 kho: extended scratch
date: 6 hours ago
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260430/202604300954.lysOjEtq-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/20260430/202604300954.lysOjEtq-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/202604300954.lysOjEtq-lkp@intel.com/
All errors (new ones prefixed by >>):
>> mm/mm_init.c:2691:2: error: call to undeclared function 'kho_extend_scratch'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
2691 | kho_extend_scratch();
| ^
1 error generated.
vim +/kho_extend_scratch +2691 mm/mm_init.c
2688
2689 void __init mm_core_init_early(void)
2690 {
> 2691 kho_extend_scratch();
2692 hugetlb_cma_reserve();
2693 hugetlb_bootmem_alloc();
2694
2695 free_area_init();
2696 }
2697
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-30 7:52 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=202604300954.lysOjEtq-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pratyush@kernel.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