From: kernel test robot <lkp@intel.com>
To: David Hildenbrand <david@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [davidhildenbrand:virtio-mem-pg-offline 3/5] mm/mm_init.c:2508:9: error: implicit declaration of function '_free_pages_core'; did you mean '__free_pages_core'?
Date: Fri, 7 Jun 2024 00:41:10 +0800 [thread overview]
Message-ID: <202406070022.hbhs2wAc-lkp@intel.com> (raw)
tree: https://github.com/davidhildenbrand/linux virtio-mem-pg-offline
head: 1816cc48b3c54139589a526b6986439600b80180
commit: 4a19cdf655855a47e0b84be7783451da60a7f9e1 [3/5] mm: pass meminit_context to __free_pages_core()
config: parisc-allnoconfig (https://download.01.org/0day-ci/archive/20240607/202406070022.hbhs2wAc-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240607/202406070022.hbhs2wAc-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/202406070022.hbhs2wAc-lkp@intel.com/
All errors (new ones prefixed by >>):
mm/mm_init.c: In function 'memblock_free_pages':
>> mm/mm_init.c:2508:9: error: implicit declaration of function '_free_pages_core'; did you mean '__free_pages_core'? [-Werror=implicit-function-declaration]
2508 | _free_pages_core(page, order, MEMINIT_EARLY);
| ^~~~~~~~~~~~~~~~
| __free_pages_core
cc1: some warnings being treated as errors
vim +2508 mm/mm_init.c
2482
2483 void __init memblock_free_pages(struct page *page, unsigned long pfn,
2484 unsigned int order)
2485 {
2486 if (IS_ENABLED(CONFIG_DEFERRED_STRUCT_PAGE_INIT)) {
2487 int nid = early_pfn_to_nid(pfn);
2488
2489 if (!early_page_initialised(pfn, nid))
2490 return;
2491 }
2492
2493 if (!kmsan_memblock_free_pages(page, order)) {
2494 /* KMSAN will take care of these pages. */
2495 return;
2496 }
2497
2498 /* pages were reserved and not allocated */
2499 if (mem_alloc_profiling_enabled()) {
2500 union codetag_ref *ref = get_page_tag_ref(page);
2501
2502 if (ref) {
2503 set_codetag_empty(ref);
2504 put_page_tag_ref(ref);
2505 }
2506 }
2507
> 2508 _free_pages_core(page, order, MEMINIT_EARLY);
2509 }
2510
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-06-06 16:43 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=202406070022.hbhs2wAc-lkp@intel.com \
--to=lkp@intel.com \
--cc=david@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.