All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android15-6.6 2/2] mm/page_alloc.c:1729:6: warning: no previous prototype for 'prep_new_page'
Date: Sat, 04 Jul 2026 10:51:14 +0800	[thread overview]
Message-ID: <202607041026.SYysmHf4-lkp@intel.com> (raw)

tree:   https://android.googlesource.com/kernel/common android15-6.6
head:   067e5e6bd6445f97dfbbf71bc3693d1bea71972d
commit: 3eb552620ce010b786bdc76a74722b9339d9c0ba [2/2] ANDROID: export symbols for vendor module
config: arm-allyesconfig (https://download.01.org/0day-ci/archive/20260704/202607041026.SYysmHf4-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260704/202607041026.SYysmHf4-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/202607041026.SYysmHf4-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> mm/page_alloc.c:1729:6: warning: no previous prototype for 'prep_new_page' [-Wmissing-prototypes]
    1729 | void prep_new_page(struct page *page, unsigned int order, gfp_t gfp_flags,
         |      ^~~~~~~~~~~~~


vim +/prep_new_page +1729 mm/page_alloc.c

  1728	
> 1729	void prep_new_page(struct page *page, unsigned int order, gfp_t gfp_flags,
  1730								unsigned int alloc_flags)
  1731	{
  1732		post_alloc_hook(page, order, gfp_flags);
  1733	
  1734		if (order && (gfp_flags & __GFP_COMP))
  1735			prep_compound_page(page, order);
  1736	
  1737		/*
  1738		 * page is set pfmemalloc when ALLOC_NO_WATERMARKS was necessary to
  1739		 * allocate the page. The expectation is that the caller is taking
  1740		 * steps that will free more memory. The caller should avoid the page
  1741		 * being used for !PFMEMALLOC purposes.
  1742		 */
  1743		if (alloc_flags & ALLOC_NO_WATERMARKS)
  1744			set_page_pfmemalloc(page);
  1745		else
  1746			clear_page_pfmemalloc(page);
  1747		trace_android_vh_test_clear_look_around_ref(page);
  1748	}
  1749	EXPORT_SYMBOL_GPL(prep_new_page);
  1750	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-07-04  2:51 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=202607041026.SYysmHf4-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.