From: kernel test robot <lkp@intel.com>
To: Hongbo Li <lihongbo22@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev,
Christian Brauner <brauner@kernel.org>,
Gao Xiang <hsiangkao@linux.alibaba.com>,
"Darrick J. Wong" <djwong@kernel.org>
Subject: [linux-next:master 5773/9539] Warning: fs/iomap/buffered-io.c:624 function parameter 'private' not described in 'iomap_readahead'
Date: Mon, 26 Jan 2026 11:56:42 +0800 [thread overview]
Message-ID: <202601261111.vIL9rhgD-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: ca3a02fda4da8e2c1cb6baee5d72352e9e2cfaea
commit: 8806f279244bf300dca2c99735d5a51cd24b86df [5773/9539] iomap: stash iomap read ctx in the private field of iomap_iter
config: x86_64-rhel-9.4 (https://download.01.org/0day-ci/archive/20260126/202601261111.vIL9rhgD-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260126/202601261111.vIL9rhgD-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/202601261111.vIL9rhgD-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: fs/iomap/buffered-io.c:624 function parameter 'private' not described in 'iomap_readahead'
>> Warning: fs/iomap/buffered-io.c:624 function parameter 'private' not described in 'iomap_readahead'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-01-26 3:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 3:56 kernel test robot [this message]
2026-01-26 4:01 ` [linux-next:master 5773/9539] Warning: fs/iomap/buffered-io.c:624 function parameter 'private' not described in 'iomap_readahead' Gao Xiang
2026-01-26 6:18 ` Hongbo Li
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=202601261111.vIL9rhgD-lkp@intel.com \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=hsiangkao@linux.alibaba.com \
--cc=lihongbo22@huawei.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.