Hi Peng, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [cannot apply to v5.3 next-20190920] [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/Peng-Fan/mailbox-arm-introduce-smc-triggered-mailbox/20190924-091652 config: sh-allmodconfig (attached as .config) compiler: sh4-linux-gcc (GCC) 7.4.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=7.4.0 make.cross ARCH=sh If you fix the issue, kindly add following tag Reported-by: kbuild test robot <lkp@xxxxxxxxx> All errors (new ones prefixed by >>): In file included from <command-line>:0:0: >> include/linux/mailbox/arm-smccc-mbox.h:17:3: error: unknown type name 'u32' u32 args_smccc32[6]; ^~~ >> include/linux/mailbox/arm-smccc-mbox.h:18:3: error: unknown type name 'u64' u64 args_smccc64[6]; ^~~ vim +/u32 +17 include/linux/mailbox/arm-smccc-mbox.h 5 6 /** 7 * struct arm_smccc_mbox_cmd - ARM SMCCC message structure 8 * @function_id: function id passed from client, If mbox 9 * DT has arm,func-id property, the driver will use 10 * that one. 11 * @args_smccc32/64: actual usage of registers is up to the protocol 12 * (within the SMCCC limits) 13 */ 14 struct arm_smccc_mbox_cmd { 15 unsigned int function_id; 16 union { > 17 u32 args_smccc32[6]; > 18 u64 args_smccc64[6]; 19 }; 20 }; 21 --- 0-DAY kernel test infrastructure Open Source Technology Center https://lists.01.org/pipermail/kbuild-all Intel Corporation
Attachment:
.config.gz
Description: application/gzip