From: kernel test robot <lkp@intel.com>
To: Kanchan Joshi <joshi.k@samsung.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Jens Axboe <axboe@kernel.dk>, Anuj Gupta <anuj20.g@samsung.com>,
Christoph Hellwig <hch@lst.de>
Subject: [axboe-block:for-5.19/io_uring-passthrough 90/91] drivers/nvme/host/multipath.c:440:27: error: initialization of 'int (*)(struct io_uring_cmd *, unsigned int)' from incompatible pointer type 'void (*)(struct io_uring_cmd *, unsigned int)'
Date: Fri, 6 May 2022 08:41:14 +0800 [thread overview]
Message-ID: <202205060818.JVCJuprZ-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-5.19/io_uring-passthrough
head: 5216380430fe99277e745867b6d9232e09dd1a21
commit: cedc754a8590e5531ec9e85a44e6fe1e296d10c4 [90/91] nvme: wire-up uring-cmd support for io-passthru on char-device.
config: i386-debian-10.3 (https://download.01.org/0day-ci/archive/20220506/202205060818.JVCJuprZ-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.2.0-20) 11.2.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/?id=cedc754a8590e5531ec9e85a44e6fe1e296d10c4
git remote add axboe-block https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
git fetch --no-tags axboe-block for-5.19/io_uring-passthrough
git checkout cedc754a8590e5531ec9e85a44e6fe1e296d10c4
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash drivers/nvme/host/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/nvme/host/multipath.c:440:27: error: initialization of 'int (*)(struct io_uring_cmd *, unsigned int)' from incompatible pointer type 'void (*)(struct io_uring_cmd *, unsigned int)' [-Werror=incompatible-pointer-types]
440 | .uring_cmd = nvme_ns_head_chr_uring_cmd,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/nvme/host/multipath.c:440:27: note: (near initialization for 'nvme_ns_head_chr_fops.uring_cmd')
cc1: some warnings being treated as errors
vim +440 drivers/nvme/host/multipath.c
433
434 static const struct file_operations nvme_ns_head_chr_fops = {
435 .owner = THIS_MODULE,
436 .open = nvme_ns_head_chr_open,
437 .release = nvme_ns_head_chr_release,
438 .unlocked_ioctl = nvme_ns_head_chr_ioctl,
439 .compat_ioctl = compat_ptr_ioctl,
> 440 .uring_cmd = nvme_ns_head_chr_uring_cmd,
441 };
442
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-05-06 0: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=202205060818.JVCJuprZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=anuj20.g@samsung.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=joshi.k@samsung.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
/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