From: kbuild test robot <lkp@intel.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: kbuild-all@01.org, linux-nfs@vger.kernel.org
Subject: [nfs:ioctl 3/5] fs/nfs/ioctl.c:112:25: error: 'const struct nfs_rpc_ops' has no member named 'return_delegation'
Date: Thu, 6 Sep 2018 04:59:33 +0800 [thread overview]
Message-ID: <201809060429.sHX7uzeC%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
tree: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git ioctl
head: 935e0ffbdaadacdfe519c891d36125f7e7d3d69a
commit: 57e59890e141c3cb14482736c0fbb26229c129a9 [3/5] NFS: Allow users to return the delegation
config: i386-randconfig-a3-201835 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
git checkout 57e59890e141c3cb14482736c0fbb26229c129a9
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
fs/nfs/ioctl.c: In function 'nfs_ioctl_return_delegation':
>> fs/nfs/ioctl.c:112:25: error: 'const struct nfs_rpc_ops' has no member named 'return_delegation'
return NFS_PROTO(inode)->return_delegation(inode);
^
fs/nfs/ioctl.c:113:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
vim +112 fs/nfs/ioctl.c
107
108 static long nfs_ioctl_return_delegation(struct file *filp)
109 {
110 struct inode *inode = filp->f_path.dentry->d_inode;
111
> 112 return NFS_PROTO(inode)->return_delegation(inode);
113 }
114
---
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: 28659 bytes --]
next reply other threads:[~2018-09-06 1:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 20:59 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-08 18:36 [nfs:ioctl 3/5] fs/nfs/ioctl.c:112:25: error: 'const struct nfs_rpc_ops' has no member named 'return_delegation' kbuild test robot
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=201809060429.sHX7uzeC%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=Trond.Myklebust@netapp.com \
--cc=kbuild-all@01.org \
--cc=linux-nfs@vger.kernel.org \
/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).