From: kernel test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Vitaly Wool <vitaly.wool@konsulko.se>
Subject: [akpm-mm:mm-new 279/316] mm/zblock.c:126: warning: Excess function parameter 'ops' description in 'zblock_create_pool'
Date: Tue, 6 May 2025 07:51:00 +0800 [thread overview]
Message-ID: <202505060720.ClN2d7w7-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-new
head: 0a7288c8a39a20b3bf12485dffa90d0ceebe96ab
commit: d003bacb573258e40d630fe7e5b8ba8f4bd0b851 [279/316] mm-add-zblock-allocator-fix
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20250506/202505060720.ClN2d7w7-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250506/202505060720.ClN2d7w7-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/202505060720.ClN2d7w7-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> mm/zblock.c:126: warning: Excess function parameter 'ops' description in 'zblock_create_pool'
vim +126 mm/zblock.c
0822617662c8b1 Vitaly Wool 2025-04-12 113
0822617662c8b1 Vitaly Wool 2025-04-12 114 /*****************
0822617662c8b1 Vitaly Wool 2025-04-12 115 * API Functions
0822617662c8b1 Vitaly Wool 2025-04-12 116 *****************/
0822617662c8b1 Vitaly Wool 2025-04-12 117 /**
0822617662c8b1 Vitaly Wool 2025-04-12 118 * zblock_create_pool() - create a new zblock pool
0822617662c8b1 Vitaly Wool 2025-04-12 119 * @gfp: gfp flags when allocating the zblock pool structure
0822617662c8b1 Vitaly Wool 2025-04-12 120 * @ops: user-defined operations for the zblock pool
0822617662c8b1 Vitaly Wool 2025-04-12 121 *
0822617662c8b1 Vitaly Wool 2025-04-12 122 * Return: pointer to the new zblock pool or NULL if the metadata allocation
0822617662c8b1 Vitaly Wool 2025-04-12 123 * failed.
0822617662c8b1 Vitaly Wool 2025-04-12 124 */
0822617662c8b1 Vitaly Wool 2025-04-12 125 static struct zblock_pool *zblock_create_pool(gfp_t gfp)
0822617662c8b1 Vitaly Wool 2025-04-12 @126 {
0822617662c8b1 Vitaly Wool 2025-04-12 127 struct zblock_pool *pool;
0822617662c8b1 Vitaly Wool 2025-04-12 128 struct block_list *block_list;
0822617662c8b1 Vitaly Wool 2025-04-12 129 int i;
0822617662c8b1 Vitaly Wool 2025-04-12 130
0822617662c8b1 Vitaly Wool 2025-04-12 131 pool = kmalloc(sizeof(struct zblock_pool), gfp);
0822617662c8b1 Vitaly Wool 2025-04-12 132 if (!pool)
0822617662c8b1 Vitaly Wool 2025-04-12 133 return NULL;
0822617662c8b1 Vitaly Wool 2025-04-12 134
0822617662c8b1 Vitaly Wool 2025-04-12 135 /* init each block list */
0822617662c8b1 Vitaly Wool 2025-04-12 136 for (i = 0; i < ARRAY_SIZE(block_desc); i++) {
0822617662c8b1 Vitaly Wool 2025-04-12 137 block_list = &pool->block_lists[i];
0822617662c8b1 Vitaly Wool 2025-04-12 138 spin_lock_init(&block_list->lock);
0822617662c8b1 Vitaly Wool 2025-04-12 139 INIT_LIST_HEAD(&block_list->full_list);
0822617662c8b1 Vitaly Wool 2025-04-12 140 INIT_LIST_HEAD(&block_list->active_list);
0822617662c8b1 Vitaly Wool 2025-04-12 141 block_list->block_count = 0;
0822617662c8b1 Vitaly Wool 2025-04-12 142 }
0822617662c8b1 Vitaly Wool 2025-04-12 143 return pool;
0822617662c8b1 Vitaly Wool 2025-04-12 144 }
0822617662c8b1 Vitaly Wool 2025-04-12 145
:::::: The code at line 126 was first introduced by commit
:::::: 0822617662c8b165cc21923f22028976945d316a mm: add zblock allocator
:::::: TO: Vitaly Wool <vitaly.wool@konsulko.se>
:::::: CC: Andrew Morton <akpm@linux-foundation.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-05 23:52 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=202505060720.ClN2d7w7-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vitaly.wool@konsulko.se \
/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