From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android16-6.12 1/1] mm/page_alloc.c:1831:6: warning: no previous prototype for function 'prep_new_page'
Date: Thu, 02 Jul 2026 11:07:16 +0800 [thread overview]
Message-ID: <202607021102.PWyz2smJ-lkp@intel.com> (raw)
Hi Wenchao,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android16-6.12
head: 030ed2af4ba8ba50d5f3cbbc704bc93df568d84e
commit: f2c613bbd9ad3f09e4eb94bf541cdfb57423dcc9 [1/1] ANDROID: export symbol prep_new_page for vendor module
config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20260702/202607021102.PWyz2smJ-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 6cc609bb250b21b47fc7d394b4019101e9983597)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260702/202607021102.PWyz2smJ-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/202607021102.PWyz2smJ-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> mm/page_alloc.c:1831:6: warning: no previous prototype for function 'prep_new_page' [-Wmissing-prototypes]
1831 | void prep_new_page(struct page *page, unsigned int order, gfp_t gfp_flags,
| ^
mm/page_alloc.c:1831:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
1831 | void prep_new_page(struct page *page, unsigned int order, gfp_t gfp_flags,
| ^
| static
1 warning generated.
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for INTEL_MEI_ME
Depends on [n]: X86 && PCI [=y]
Selected by [m]:
- INTEL_MEI_HDCP [=m] && (DRM_I915 [=n] || DRM_XE [=m])
- INTEL_MEI_PXP [=m] && (DRM_I915 [=n] || DRM_XE [=m])
vim +/prep_new_page +1831 mm/page_alloc.c
1830
> 1831 void prep_new_page(struct page *page, unsigned int order, gfp_t gfp_flags,
1832 unsigned int alloc_flags)
1833 {
1834 post_alloc_hook(page, order, gfp_flags);
1835
1836 if (order && (gfp_flags & __GFP_COMP))
1837 prep_compound_page(page, order);
1838
1839 /*
1840 * page is set pfmemalloc when ALLOC_NO_WATERMARKS was necessary to
1841 * allocate the page. The expectation is that the caller is taking
1842 * steps that will free more memory. The caller should avoid the page
1843 * being used for !PFMEMALLOC purposes.
1844 */
1845 if (alloc_flags & ALLOC_NO_WATERMARKS)
1846 set_page_pfmemalloc(page);
1847 else
1848 clear_page_pfmemalloc(page);
1849 trace_android_vh_test_clear_look_around_ref(page);
1850 }
1851 EXPORT_SYMBOL_GPL(prep_new_page);
1852
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-02 3:08 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=202607021102.PWyz2smJ-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.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.