From: kbuild test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: kbuild-all@01.org, linux-fsdevel@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>
Subject: [vfs:T3 78/82] arch/powerpc//platforms/cell/spufs/inode.c:728:19: error: 'spufs_destroy_inode' undeclared here (not in a function); did you mean '__destroy_inode'?
Date: Tue, 14 May 2019 03:00:59 +0800 [thread overview]
Message-ID: <201905140348.bekHc3C2%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1605 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git T3
head: 8bb72026a69d4b951665d8628a61a8049fb3eb8d
commit: e62263f30a0eda8a6d13eed8584179f0c1a34da5 [78/82] vfs: Convert spufs to use the new mount API
config: powerpc-defconfig (attached as .config)
compiler: powerpc64-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
git checkout e62263f30a0eda8a6d13eed8584179f0c1a34da5
# save the attached .config to linux build tree
GCC_VERSION=7.2.0 make.cross ARCH=powerpc
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> arch/powerpc//platforms/cell/spufs/inode.c:728:19: error: 'spufs_destroy_inode' undeclared here (not in a function); did you mean '__destroy_inode'?
.destroy_inode = spufs_destroy_inode,
^~~~~~~~~~~~~~~~~~~
__destroy_inode
vim +728 arch/powerpc//platforms/cell/spufs/inode.c
724
725 static const struct super_operations spufs_ops = {
726 .alloc_inode = spufs_alloc_inode,
727 .free_inode = spufs_free_inode,
> 728 .destroy_inode = spufs_destroy_inode,
729 .statfs = simple_statfs,
730 .evict_inode = spufs_evict_inode,
731 .show_options = spufs_show_options,
732 };
733
---
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: 24249 bytes --]
reply other threads:[~2019-05-13 19: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=201905140348.bekHc3C2%lkp@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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