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-v2 11/13] Warning: io_uring/rsrc.c:1428 function parameter 'ctx' not described in 'io_register_buffers_alloc_for_file'
Date: Wed, 01 Jul 2026 04:27:44 +0200 [thread overview]
Message-ID: <202607010401.SQ6UxVG3-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git blk-iobuf-pool-v2
head: da75cc2253180af718ba0b7b3684a091b16b14fb
commit: 83df08bcb3ef8910445506a7f1e4214a12c4ead6 [11/13] io_uring: add IORING_REGISTER_BUFFERS_ALLOC_FOR_FILE (opcode 38)
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260701/202607010401.SQ6UxVG3-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260701/202607010401.SQ6UxVG3-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/202607010401.SQ6UxVG3-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: io_uring/rsrc.c:1428 function parameter 'ctx' not described in 'io_register_buffers_alloc_for_file'
>> Warning: io_uring/rsrc.c:1428 function parameter 'arg' not described in 'io_register_buffers_alloc_for_file'
>> Warning: io_uring/rsrc.c:1657 function parameter 'ioucmd' not described in 'io_uring_cmd_fixed_buf_get_imu'
>> Warning: io_uring/rsrc.c:1657 function parameter 'issue_flags' not described in 'io_uring_cmd_fixed_buf_get_imu'
>> Warning: io_uring/rsrc.c:1678 function parameter 'ioucmd' not described in 'io_uring_cmd_blk_iobuf_validate'
>> Warning: io_uring/rsrc.c:1678 function parameter 'issue_flags' not described in 'io_uring_cmd_blk_iobuf_validate'
>> Warning: io_uring/rsrc.c:1678 function parameter 'expected_q' not described in 'io_uring_cmd_blk_iobuf_validate'
>> Warning: io_uring/rsrc.c:1428 function parameter 'ctx' not described in 'io_register_buffers_alloc_for_file'
>> Warning: io_uring/rsrc.c:1428 function parameter 'arg' not described in 'io_register_buffers_alloc_for_file'
>> Warning: io_uring/rsrc.c:1657 function parameter 'ioucmd' not described in 'io_uring_cmd_fixed_buf_get_imu'
>> Warning: io_uring/rsrc.c:1657 function parameter 'issue_flags' not described in 'io_uring_cmd_fixed_buf_get_imu'
>> Warning: io_uring/rsrc.c:1678 function parameter 'ioucmd' not described in 'io_uring_cmd_blk_iobuf_validate'
>> Warning: io_uring/rsrc.c:1678 function parameter 'issue_flags' not described in 'io_uring_cmd_blk_iobuf_validate'
>> Warning: io_uring/rsrc.c:1678 function parameter 'expected_q' not described in 'io_uring_cmd_blk_iobuf_validate'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-07-01 2:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 2:27 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-01 2:18 [mcgrof:blk-iobuf-pool-v2 11/13] Warning: io_uring/rsrc.c:1428 function parameter 'ctx' not described in 'io_register_buffers_alloc_for_file' 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=202607010401.SQ6UxVG3-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 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.