From: kernel test robot <lkp@intel.com>
To: Gregory Price <gourry@gourry.net>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Gregory Price <gourry@gourry.net>
Subject: [gourryinverse:gourry_pagecache 6/6] mm/migrate.c:2753: warning: Function parameter or struct member 'folio' not described in 'promotion_candidate'
Date: Tue, 7 Jan 2025 12:32:14 +0800 [thread overview]
Message-ID: <202501071202.mCEEi2nO-lkp@intel.com> (raw)
tree: https://github.com/gourryinverse/linux gourry_pagecache
head: 0b481ba53a1ea6337129cbe63f9234a748df4843
commit: 0b481ba53a1ea6337129cbe63f9234a748df4843 [6/6] migrate,sysfs: add pagecache promotion
config: i386-buildonly-randconfig-003-20250107 (https://download.01.org/0day-ci/archive/20250107/202501071202.mCEEi2nO-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250107/202501071202.mCEEi2nO-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/202501071202.mCEEi2nO-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> mm/migrate.c:2753: warning: Function parameter or struct member 'folio' not described in 'promotion_candidate'
vim +2753 mm/migrate.c
2741
2742 /**
2743 * promotion_candidate: report a promotion candidate folio
2744 *
2745 * The folio will be isolated from LRU if selected, and task_work will
2746 * putback the folio on promotion failure.
2747 *
2748 * Candidates may not be promoted and may be returned to the LRU.
2749 *
2750 * Takes a folio reference that will be released in task work.
2751 */
2752 void promotion_candidate(struct folio *folio)
> 2753 {
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-01-07 4:32 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=202501071202.mCEEi2nO-lkp@intel.com \
--to=lkp@intel.com \
--cc=gourry@gourry.net \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox