From: kernel test robot <lkp@intel.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [jlayton:ceph-fscrypt-sparse 62/69] fs/ceph/crypto.h:233:1: error: expected identifier or '(' before '{' token
Date: Sat, 19 Mar 2022 10:58:02 +0800 [thread overview]
Message-ID: <202203191032.JfjdgbaE-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git ceph-fscrypt-sparse
head: a6125c2dec56f1f523f5009ce8b25932ba4be812
commit: 8e0977c7c0cb145079b881a6035a98bb0ce71b1b [62/69] ceph: new helper: ceph_fscrypt_decrypt_extents
config: microblaze-randconfig-s031-20220317 (https://download.01.org/0day-ci/archive/20220319/202203191032.JfjdgbaE-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 11.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git/commit/?id=8e0977c7c0cb145079b881a6035a98bb0ce71b1b
git remote add jlayton https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git
git fetch --no-tags jlayton ceph-fscrypt-sparse
git checkout 8e0977c7c0cb145079b881a6035a98bb0ce71b1b
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=microblaze SHELL=/bin/bash fs/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from fs/ceph/super.h:28,
from fs/ceph/super.c:20:
>> fs/ceph/crypto.h:233:1: error: expected identifier or '(' before '{' token
233 | {
| ^
fs/ceph/crypto.h:230:19: warning: 'ceph_fscrypt_decrypt_extents' declared 'static' but never defined [-Wunused-function]
230 | static inline int ceph_fscrypt_decrypt_extents(struct inode *inode, struct page **page,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +233 fs/ceph/crypto.h
229
230 static inline int ceph_fscrypt_decrypt_extents(struct inode *inode, struct page **page,
231 u64 off, struct ceph_sparse_extent *map,
232 u32 ext_cnt);
> 233 {
234 return 0;
235 }
236
---
0-DAY CI Kernel Test Service
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-03-19 2:59 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=202203191032.JfjdgbaE-lkp@intel.com \
--to=lkp@intel.com \
--cc=jlayton@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®