From: kernel test robot <lkp@intel.com>
To: Vitaly Wool <vitaly.wool@konsulko.se>
Cc: oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Igor Belousov <igor.b@beldev.am>
Subject: [akpm-mm:mm-new 195/196] mm/zblock.c:369:33: error: initialization of 'int (*)(void *, size_t, gfp_t, long unsigned int *, const int)' {aka 'int (*)(void *, unsigned int, unsigned int, long unsigned int *, const int)'} from incompatible pointer type 'int (*)(void *, size_t, ...
Date: Wed, 16 Apr 2025 16:58:30 +0800 [thread overview]
Message-ID: <202504161606.b5FstdkD-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-new
head: 13ef12753ee527caca620af5ab72ef6249c20622
commit: 40d54ac31c6e801d94f2563158650b69c15fbf82 [195/196] mm: add zblock allocator
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20250416/202504161606.b5FstdkD-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/20250416/202504161606.b5FstdkD-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/202504161606.b5FstdkD-lkp@intel.com/
All errors (new ones prefixed by >>):
>> mm/zblock.c:369:33: error: initialization of 'int (*)(void *, size_t, gfp_t, long unsigned int *, const int)' {aka 'int (*)(void *, unsigned int, unsigned int, long unsigned int *, const int)'} from incompatible pointer type 'int (*)(void *, size_t, gfp_t, long unsigned int *)' {aka 'int (*)(void *, unsigned int, unsigned int, long unsigned int *)'} [-Wincompatible-pointer-types]
369 | .malloc = zblock_zpool_malloc,
| ^~~~~~~~~~~~~~~~~~~
mm/zblock.c:369:33: note: (near initialization for 'zblock_zpool_driver.malloc')
vim +369 mm/zblock.c
363
364 static struct zpool_driver zblock_zpool_driver = {
365 .type = "zblock",
366 .owner = THIS_MODULE,
367 .create = zblock_zpool_create,
368 .destroy = zblock_zpool_destroy,
> 369 .malloc = zblock_zpool_malloc,
370 .free = zblock_zpool_free,
371 .obj_read_begin = zblock_zpool_read_begin,
372 .obj_read_end = zblock_zpool_read_end,
373 .obj_write = zblock_zpool_obj_write,
374 .total_pages = zblock_zpool_total_pages,
375 };
376
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-04-16 8:59 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=202504161606.b5FstdkD-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=igor.b@beldev.am \
--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 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.