Hi, [FYI, it's a private test report for your RFC patch.] [auto build test ERROR on kbuild/for-next] [also build test ERROR on linus/master next-20200406] [cannot apply to security/next-testing dm/for-next v5.6] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify the base tree in git format-patch, please see https://stackoverflow.com/a/37406982] url: https://github.com/0day-ci/linux/commits/deven-desai-linux-microsoft-com/Integrity-Policy-Enforcement-LSM-IPE/20200407-061828 base: https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git for-next config: sparc64-randconfig-a001-20200407 (attached as .config) compiler: sparc64-linux-gcc (GCC) 9.3.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=9.3.0 make.cross ARCH=sparc64 If you fix the issue, kindly add following tag as appropriate Reported-by: kbuild test robot All errors (new ones prefixed by >>): In file included from drivers/md/dm-verity-target.c:18: >> drivers/md/dm-verity-verify-sig.h:38:1: error: expected identifier or '(' before '{' token 38 | { | ^ vim +38 drivers/md/dm-verity-verify-sig.h 88cd3e6cfac915 Jaskaran Khurana 2019-07-17 36 6a8bbd6bb3b982 Deven Bowers 2020-04-06 37 int verity_verify_root_hash(const struct dm_verity *v); 88cd3e6cfac915 Jaskaran Khurana 2019-07-17 @38 { 88cd3e6cfac915 Jaskaran Khurana 2019-07-17 39 return 0; 88cd3e6cfac915 Jaskaran Khurana 2019-07-17 40 } 88cd3e6cfac915 Jaskaran Khurana 2019-07-17 41 :::::: The code at line 38 was first introduced by commit :::::: 88cd3e6cfac915f50f7aa7b699bdf053afec866e dm verity: add root hash pkcs#7 signature verification :::::: TO: Jaskaran Khurana :::::: CC: Mike Snitzer --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org