From: kernel test robot <lkp@intel.com>
To: Luis Chamberlain <mcgrof@do-not-panic.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [mcgrof:blk-iobuf-pool-v5 6/9] block/ioctl.c:958:8: error: call to undeclared function 'blk_uring_cmd_alloc_iobuf'; ISO C99 and later do not support implicit function declarations
Date: Tue, 28 Jul 2026 23:08:27 +0800 [thread overview]
Message-ID: <202607282211.C9sCcdUM-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git blk-iobuf-pool-v5
head: de80bacbf04a137715357b6a2948d9f29a18d990
commit: 37ff77d98dbfae93b246dadfe1d25b768b9e8798 [6/9] block: add a uring command for pool-backed fixed buffers
config: arm-pxa168_defconfig (https://download.01.org/0day-ci/archive/20260728/202607282211.C9sCcdUM-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 890b11e09e45e9d8b29f2f94f22052be3934e757)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260728/202607282211.C9sCcdUM-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/202607282211.C9sCcdUM-lkp@intel.com/
All errors (new ones prefixed by >>):
>> block/ioctl.c:958:8: error: call to undeclared function 'blk_uring_cmd_alloc_iobuf'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
958 | ret = blk_uring_cmd_alloc_iobuf(cmd, pool, buf_index, len, issue_flags);
| ^
block/ioctl.c:958:8: note: did you mean 'blkdev_cmd_alloc_iobuf'?
block/ioctl.c:948:12: note: 'blkdev_cmd_alloc_iobuf' declared here
948 | static int blkdev_cmd_alloc_iobuf(struct io_uring_cmd *cmd,
| ^
949 | struct block_device *bdev, u64 buf_index,
950 | u64 len, unsigned int issue_flags)
951 | {
952 | struct blk_iobuf_pool *pool;
953 | int ret;
954 |
955 | pool = blk_queue_get_iobuf_pool(bdev_get_queue(bdev));
956 | if (!pool)
957 | return -EOPNOTSUPP;
958 | ret = blk_uring_cmd_alloc_iobuf(cmd, pool, buf_index, len, issue_flags);
| ~~~~~~~~~~~~~~~~~~~~~~~~~
| blkdev_cmd_alloc_iobuf
1 error generated.
vim +/blk_uring_cmd_alloc_iobuf +958 block/ioctl.c
947
948 static int blkdev_cmd_alloc_iobuf(struct io_uring_cmd *cmd,
949 struct block_device *bdev, u64 buf_index,
950 u64 len, unsigned int issue_flags)
951 {
952 struct blk_iobuf_pool *pool;
953 int ret;
954
955 pool = blk_queue_get_iobuf_pool(bdev_get_queue(bdev));
956 if (!pool)
957 return -EOPNOTSUPP;
> 958 ret = blk_uring_cmd_alloc_iobuf(cmd, pool, buf_index, len, issue_flags);
959 blk_iobuf_pool_put(pool);
960 return ret;
961 }
962
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-07-28 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 15:08 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-28 0:17 [mcgrof:blk-iobuf-pool-v5 6/9] block/ioctl.c:958:8: error: call to undeclared function 'blk_uring_cmd_alloc_iobuf'; ISO C99 and later do not support implicit function declarations kernel test robot
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=202607282211.C9sCcdUM-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=mcgrof@do-not-panic.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox