Hi Michael, I love your patch! Yet something to improve:
[auto build test ERROR on powerpc/next] [also build test ERROR on v4.16-rc7 next-20180326] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Michael-Ellerman/powerpc-Add-security-feature-flags-for-Spectre-Meltdown/20180327-041008 base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next config: powerpc-g5_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 # save the attached .config to linux build tree make.cross ARCH=powerpc Note: the linux-review/Michael-Ellerman/powerpc-Add-security-feature-flags-for-Spectre-Meltdown/20180327-041008 HEAD 95772a19ac473c1aa27b1e5e038791da104b6a06 builds fine. It only hurts bisectibility. All errors (new ones prefixed by >>): In file included from arch/powerpc/kernel/security.c:7:0: >> arch/powerpc/include/asm/security_features.h:24:15: error: unknown type name >> 'bool' static inline bool security_ftr_enabled(unsigned long feature) ^~~~ >> arch/powerpc/kernel/security.c:10:41: error: expected '=', ',', ';', 'asm' >> or '__attribute__' before '__read_mostly' unsigned long powerpc_security_features __read_mostly = \ ^~~~~~~~~~~~~ vim +/bool +24 arch/powerpc/include/asm/security_features.h 23 > 24 static inline bool security_ftr_enabled(unsigned long feature) 25 { 26 return !!(powerpc_security_features & feature); 27 } 28 --- 0-DAY kernel test infrastructure Open Source Technology Center https://lists.01.org/pipermail/kbuild-all Intel Corporation
.config.gz
Description: application/gzip
