All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Gregory Price <gourry@gourry.net>
Cc: oe-kbuild-all@lists.linux.dev, Gregory Price <gourry@gourry.net>
Subject: [gourryinverse:gourry_pagecache 5/5] mm/migrate.c:2779: warning: Function parameter or struct member 'folio' not described in 'promotion_candidate'
Date: Sat, 22 Mar 2025 06:39:29 +0800	[thread overview]
Message-ID: <202503220608.cRFEllb9-lkp@intel.com> (raw)

tree:   https://github.com/gourryinverse/linux gourry_pagecache
head:   a83d4b477373194ebc680bcd0123bfbbc010dddb
commit: a83d4b477373194ebc680bcd0123bfbbc010dddb [5/5] migrate,sysfs: add pagecache promotion
config: csky-randconfig-001-20250322 (https://download.01.org/0day-ci/archive/20250322/202503220608.cRFEllb9-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250322/202503220608.cRFEllb9-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/202503220608.cRFEllb9-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> mm/migrate.c:2779: warning: Function parameter or struct member 'folio' not described in 'promotion_candidate'


vim +2779 mm/migrate.c

  2767	
  2768	/**
  2769	 * promotion_candidate: report a promotion candidate folio
  2770	 *
  2771	 * The folio will be isolated from LRU if selected, and task_work will
  2772	 * putback the folio on promotion failure.
  2773	 *
  2774	 * Candidates may not be promoted and may be returned to the LRU.
  2775	 *
  2776	 * Takes a folio reference that will be released in task work.
  2777	 */
  2778	void promotion_candidate(struct folio *folio)
> 2779	{

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

                 reply	other threads:[~2025-03-21 22:40 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=202503220608.cRFEllb9-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=gourry@gourry.net \
    --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.