From: kernel test robot <lkp@intel.com>
To: Goldwyn Rodrigues <rgoldwyn@suse.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [goldwynr:iomap 24/33] fs/btrfs/file.c:485:22: error: initialization of 'void (*)(struct inode *, loff_t, unsigned int, struct page *)' {aka 'void (*)(struct inode *, long long int, unsigned int, struct page *)'} from incompatible pointer type 'void (*)(struct inode *, loff...
Date: Thu, 30 Dec 2021 13:52:27 +0800 [thread overview]
Message-ID: <202112301342.KO6jKDK5-lkp@intel.com> (raw)
tree: https://github.com/goldwynr/linux iomap
head: 30c74a8c201365178cae26d0d7aefa120c3245ab
commit: 528f37bbbb59a7cf5ec08a7512eb7f86904e3684 [24/33] btrfs: define iomap_page_ops
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20211230/202112301342.KO6jKDK5-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/goldwynr/linux/commit/528f37bbbb59a7cf5ec08a7512eb7f86904e3684
git remote add goldwynr https://github.com/goldwynr/linux
git fetch --no-tags goldwynr iomap
git checkout 528f37bbbb59a7cf5ec08a7512eb7f86904e3684
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=m68k SHELL=/bin/bash fs/btrfs/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Note: the goldwynr/iomap HEAD 30c74a8c201365178cae26d0d7aefa120c3245ab builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
>> fs/btrfs/file.c:485:22: error: initialization of 'void (*)(struct inode *, loff_t, unsigned int, struct page *)' {aka 'void (*)(struct inode *, long long int, unsigned int, struct page *)'} from incompatible pointer type 'void (*)(struct inode *, loff_t, unsigned int, struct page *, struct iomap *)' {aka 'void (*)(struct inode *, long long int, unsigned int, struct page *, struct iomap *)'} [-Werror=incompatible-pointer-types]
485 | .page_done = btrfs_page_done,
| ^~~~~~~~~~~~~~~
fs/btrfs/file.c:485:22: note: (near initialization for 'btrfs_iomap_page_ops.page_done')
fs/btrfs/file.c: In function 'btrfs_buffered_iomap_end':
fs/btrfs/file.c:1715:29: error: 'bi' redeclared as different kind of symbol
1715 | struct btrfs_iomap *bi = iomap->private;
| ^~
fs/btrfs/file.c:1712:69: note: previous definition of 'bi' with type 'struct btrfs_iomap *'
1712 | loff_t length, ssize_t written, struct btrfs_iomap *bi)
| ~~~~~~~~~~~~~~~~~~~~^~
fs/btrfs/file.c:1715:34: error: 'iomap' undeclared (first use in this function)
1715 | struct btrfs_iomap *bi = iomap->private;
| ^~~~~
fs/btrfs/file.c:1715:34: note: each undeclared identifier is reported only once for each function it appears in
At top level:
fs/btrfs/file.c:484:36: warning: 'btrfs_iomap_page_ops' defined but not used [-Wunused-const-variable=]
484 | static const struct iomap_page_ops btrfs_iomap_page_ops = {
| ^~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +485 fs/btrfs/file.c
483
484 static const struct iomap_page_ops btrfs_iomap_page_ops = {
> 485 .page_done = btrfs_page_done,
486 };
487
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-12-30 5:52 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=202112301342.KO6jKDK5-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rgoldwyn@suse.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
all inboxes | Powered by JetHome®