From: kernel test robot <lkp@intel.com>
To: aubrey.li@linux.intel.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [anolis-intel-cloud:intel-6.6-DMR-ISA-ANBZ35251 7/7] mm/page_alloc.c:297:20: warning: 'add_to_free_list' declared 'static' but never defined
Date: Fri, 15 May 2026 02:52:59 +0800 [thread overview]
Message-ID: <202605150216.uSLaJApy-lkp@intel.com> (raw)
Hi Johannes,
FYI, the error/warning still remains.
tree: https://gitee.com/anolis/intel-cloud-kernel.git intel-6.6-DMR-ISA-ANBZ35251
head: 1b8b6044ea621040ede1783279f18a666da924a8
commit: dce9170c150f27ea23a2a52e539cc02b6957b595 [7/7] mm: page_alloc: batch vmstat updates in expand()
config: x86_64-allnoconfig (https://download.01.org/0day-ci/archive/20260515/202605150216.uSLaJApy-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.4.0-5) 12.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260515/202605150216.uSLaJApy-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/202605150216.uSLaJApy-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> mm/page_alloc.c:297:20: warning: 'add_to_free_list' declared 'static' but never defined [-Wunused-function]
297 | static inline void add_to_free_list(struct page *page, struct zone *zone,
| ^~~~~~~~~~~~~~~~
vim +297 mm/page_alloc.c
418508c13222ddb Miklos Szeredi 2007-05-23 292
dcdfdd40fa82b67 Kirill A. Shutemov 2023-06-06 293 static bool page_contains_unaccepted(struct page *page, unsigned int order);
dcdfdd40fa82b67 Kirill A. Shutemov 2023-06-06 294 static void accept_page(struct page *page, unsigned int order);
b77471c6760a22d Kirill A. Shutemov 2024-08-09 295 static bool cond_accept_memory(struct zone *zone, unsigned int order);
dcdfdd40fa82b67 Kirill A. Shutemov 2023-06-06 296 static bool __free_unaccepted(struct page *page);
8c8774fcbaf4763 Johannes Weiner 2024-03-20 @297 static inline void add_to_free_list(struct page *page, struct zone *zone,
8c8774fcbaf4763 Johannes Weiner 2024-03-20 298 unsigned int order, int migratetype,
8c8774fcbaf4763 Johannes Weiner 2024-03-20 299 bool tail);
dcdfdd40fa82b67 Kirill A. Shutemov 2023-06-06 300
:::::: The code at line 297 was first introduced by commit
:::::: 8c8774fcbaf47634f07ee957e9cd9403f5e0ce2c mm: page_alloc: consolidate free page accounting
:::::: TO: Johannes Weiner <hannes@cmpxchg.org>
:::::: CC: 小龙 <wenqing.ly@alibaba-inc.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-14 18:53 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=202605150216.uSLaJApy-lkp@intel.com \
--to=lkp@intel.com \
--cc=aubrey.li@linux.intel.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.