From: kernel test robot <lkp@intel.com>
To: Ojaswin Mujoo <ojaswin@linux.ibm.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
0day robot <lkp@intel.com>,
"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
Subject: Warning: fs/iomap/buffered-io.c:1197 expecting prototype for iomap_writethrough_begin(). Prototype was for iomap_folio_prepare_writethrough() instead
Date: Fri, 10 Apr 2026 20:00:42 +0200 [thread overview]
Message-ID: <202604101906.2hS8zSW9-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Ojaswin-Mujoo/mm-Refactor-folio_clear_dirty_for_io/20260410-201946
head: 97f848afc87b3d743b0b4cb27f081bfa48c2329a
commit: c85ff7e2dd1ce5c4d380ea54527f307059e3fbd9 iomap: Add initial support for buffered RWF_WRITETHROUGH
date: 5 hours ago
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260410/202604101906.2hS8zSW9-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260410/202604101906.2hS8zSW9-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/202604101906.2hS8zSW9-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: fs/iomap/buffered-io.c:1197 expecting prototype for iomap_writethrough_begin(). Prototype was for iomap_folio_prepare_writethrough() instead
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-10 18:01 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=202604101906.2hS8zSW9-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
/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