From: kernel test robot <lkp@intel.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [koverstreet-bcachefs:master 187/194] mm/shrinker.c:834: warning: Function parameter or struct member 'out' not described in 'shrinkers_to_text'
Date: Tue, 13 May 2025 11:41:36 +0800 [thread overview]
Message-ID: <202505131133.cevdwGyc-lkp@intel.com> (raw)
tree: https://github.com/koverstreet/bcachefs master
head: a26f34c344d8314acf0c28e20166a4a090dbd298
commit: 78e5e613459733c8cc38dfcccb1e8133ddfbbc63 [187/194] mm: shrinker: Add a .to_text() method for shrinkers
config: arm-randconfig-002-20250513 (https://download.01.org/0day-ci/archive/20250513/202505131133.cevdwGyc-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250513/202505131133.cevdwGyc-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/202505131133.cevdwGyc-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> mm/shrinker.c:834: warning: Function parameter or struct member 'out' not described in 'shrinkers_to_text'
vim +834 mm/shrinker.c
826
827 /**
828 * shrinkers_to_text - Report on shrinkers with highest usage
829 *
830 * This reports on the top 10 shrinkers, by object counts, in sorted order:
831 * intended to be used for OOM reporting.
832 */
833 void shrinkers_to_text(struct seq_buf *out)
> 834 {
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-13 3:42 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=202505131133.cevdwGyc-lkp@intel.com \
--to=lkp@intel.com \
--cc=kent.overstreet@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 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.