From: kbuild test robot <lkp@intel.com>
To: Niels de Vos <ndevos@redhat.com>
Cc: kbuild-all@01.org, Miklos Szeredi <miklos@szeredi.hu>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Niels de Vos <ndevos@redhat.com>
Subject: Re: [PATCH] fuse: add support for copy_file_range()
Date: Wed, 27 Jun 2018 16:25:31 +0800 [thread overview]
Message-ID: <201806271659.CGX9gfFK%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180627074534.7307-1-ndevos@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2092 bytes --]
Hi Niels,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on fuse/for-next]
[also build test ERROR on v4.18-rc2 next-20180626]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Niels-de-Vos/fuse-add-support-for-copy_file_range/20180627-155404
base: https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-next
config: mips-allyesconfig (attached as .config)
compiler: mips-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.2.0 make.cross ARCH=mips
All errors (new ones prefixed by >>):
>> fs/fuse/file.c:3092:21: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
.copy_file_range = fuse_copy_file_range,
^~~~~~~~~~~~~~~~~~~~
fs/fuse/file.c:3092:21: note: (near initialization for 'fuse_file_operations.copy_file_range')
cc1: some warnings being treated as errors
vim +3092 fs/fuse/file.c
3075
3076 static const struct file_operations fuse_file_operations = {
3077 .llseek = fuse_file_llseek,
3078 .read_iter = fuse_file_read_iter,
3079 .write_iter = fuse_file_write_iter,
3080 .mmap = fuse_file_mmap,
3081 .open = fuse_open,
3082 .flush = fuse_flush,
3083 .release = fuse_release,
3084 .fsync = fuse_fsync,
3085 .lock = fuse_file_lock,
3086 .flock = fuse_file_flock,
3087 .splice_read = generic_file_splice_read,
3088 .unlocked_ioctl = fuse_file_ioctl,
3089 .compat_ioctl = fuse_file_compat_ioctl,
3090 .poll = fuse_file_poll,
3091 .fallocate = fuse_file_fallocate,
> 3092 .copy_file_range = fuse_copy_file_range,
3093 };
3094
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 56512 bytes --]
next prev parent reply other threads:[~2018-06-27 8:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 7:45 [PATCH] fuse: add support for copy_file_range() Niels de Vos
2018-06-27 8:20 ` kbuild test robot
2018-06-27 8:25 ` kbuild test robot [this message]
2018-06-27 8:46 ` [PATCH v2] " Niels de Vos
2018-06-29 12:16 ` Niels de Vos
2018-06-29 12:53 ` [PATCH v3] " Niels de Vos
2018-08-06 10:46 ` Niels de Vos
2018-08-07 12:02 ` Miklos Szeredi
2018-08-21 10:12 ` Niels de Vos
2018-08-21 12:36 ` [PATCH v4] " Niels de Vos
2018-10-01 9:21 ` Miklos Szeredi
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=201806271659.CGX9gfFK%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=ndevos@redhat.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;
as well as URLs for NNTP newsgroup(s).