From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [dhowells-fs:netfs-next 23/23] fs/nfs/fscache.c:397:35: error: initialization of 'int (*)(struct netfs_io_subrequest *)' from incompatible pointer type 'void (*)(struct netfs_io_subrequest *)'
Date: Thu, 16 Jul 2026 02:39:02 +0200 [thread overview]
Message-ID: <202607160258.0saZpeQy-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git netfs-next
head: 796ea75f9f613fed6508719a8a1a71e3b1aededc
commit: 796ea75f9f613fed6508719a8a1a71e3b1aededc [23/23] netfs: Combine prepare and issue ops and grab the buffers on request
config: x86_64-rhel-9.4-bpf (https://download.01.org/0day-ci/archive/20260716/202607160258.0saZpeQy-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/20260716/202607160258.0saZpeQy-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/202607160258.0saZpeQy-lkp@intel.com/
All errors (new ones prefixed by >>):
>> fs/nfs/fscache.c:397:35: error: initialization of 'int (*)(struct netfs_io_subrequest *)' from incompatible pointer type 'void (*)(struct netfs_io_subrequest *)' [-Wincompatible-pointer-types]
397 | .issue_read = nfs_netfs_issue_read,
| ^~~~~~~~~~~~~~~~~~~~
fs/nfs/fscache.c:397:35: note: (near initialization for 'nfs_netfs_ops.issue_read')
vim +397 fs/nfs/fscache.c
000dbe0bec058c Dave Wysochanski 2023-02-20 393
000dbe0bec058c Dave Wysochanski 2023-02-20 394 const struct netfs_request_ops nfs_netfs_ops = {
000dbe0bec058c Dave Wysochanski 2023-02-20 395 .init_request = nfs_netfs_init_request,
000dbe0bec058c Dave Wysochanski 2023-02-20 396 .free_request = nfs_netfs_free_request,
000dbe0bec058c Dave Wysochanski 2023-02-20 @397 .issue_read = nfs_netfs_issue_read,
:::::: The code at line 397 was first introduced by commit
:::::: 000dbe0bec058cbf2ca9e156e4a5584f5158b0f9 NFS: Convert buffered read paths to use netfs when fscache is enabled
:::::: TO: Dave Wysochanski <dwysocha@redhat.com>
:::::: CC: Anna Schumaker <Anna.Schumaker@Netapp.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-16 0:39 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=202607160258.0saZpeQy-lkp@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.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.