From: kernel test robot <lkp@intel.com>
To: Muchun Song <songmuchun@bytedance.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
0day robot <lkp@intel.com>
Subject: Warning: mm/memory_hotplug.c:586 function parameter 'pgmap' not described in '__remove_pages'
Date: Sat, 02 May 2026 22:57:29 +0200 [thread overview]
Message-ID: <202605022258.E1bRDIm9-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Muchun-Song/mm-sparse-vmemmap-Fix-vmemmap-accounting-underflow/20260421-132535
head: dc0177fc2cee4d3ad5682369d961087baf084ece
commit: c3a62066e7b934b30859a8dbe3976202bde93d16 mm/sparse-vmemmap: Pass @pgmap argument to memory deactivation paths
date: 12 days ago
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260502/202605022258.E1bRDIm9-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/20260502/202605022258.E1bRDIm9-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/202605022258.E1bRDIm9-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: mm/memory_hotplug.c:586 function parameter 'pgmap' not described in '__remove_pages'
>> Warning: mm/memory_hotplug.c:586 function parameter 'pgmap' not described in '__remove_pages'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-02 20:58 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=202605022258.E1bRDIm9-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=songmuchun@bytedance.com \
/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