From: kbuild test robot <lkp@intel.com>
To: Trond Myklebust <trond.myklebust@hammerspace.com>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
linux-nfs@vger.kernel.org
Subject: [nfs:testing 48/54] fs/nfs/pnfs.h:808:28: error: no member named 'commits' in 'struct pnfs_ds_commit_info'
Date: Wed, 25 Mar 2020 23:47:04 +0800 [thread overview]
Message-ID: <202003252301.mJcHYctS%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1844 bytes --]
tree: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git testing
head: 21b71e249eabc75f6db7fb1ff83ce9fc34b09828
commit: 0e648259eac31aaf3922faa9874ab797ed82e11d [48/54] NFS/pNFS: Clean up pNFS commit operations
config: x86_64-defconfig (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 2093fdd429d52348e08969180ac6b1e705fc4ff6)
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 0e648259eac31aaf3922faa9874ab797ed82e11d
# save the attached .config to linux build tree
COMPILER=clang make.cross ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from fs/nfs/nfs4client.c:19:
>> fs/nfs/pnfs.h:808:28: error: no member named 'commits' in 'struct pnfs_ds_commit_info'
INIT_LIST_HEAD(&fl_cinfo->commits);
~~~~~~~~ ^
1 error generated.
--
In file included from fs/nfs/direct.c:61:
>> fs/nfs/pnfs.h:808:28: error: no member named 'commits' in 'struct pnfs_ds_commit_info'
INIT_LIST_HEAD(&fl_cinfo->commits);
~~~~~~~~ ^
fs/nfs/direct.c:208:33: error: no member named 'commits' in 'struct pnfs_ds_commit_info'
INIT_LIST_HEAD(&dreq->ds_cinfo.commits);
~~~~~~~~~~~~~~ ^
2 errors generated.
vim +808 fs/nfs/pnfs.h
804
805 static inline void
806 pnfs_init_ds_commit_info(struct pnfs_ds_commit_info *fl_cinfo, struct inode *inode)
807 {
> 808 INIT_LIST_HEAD(&fl_cinfo->commits);
809 }
810
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 29215 bytes --]
reply other threads:[~2020-03-25 15:47 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=202003252301.mJcHYctS%lkp@intel.com \
--to=lkp@intel.com \
--cc=clang-built-linux@googlegroups.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@hammerspace.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).