Hi Hari, [auto build test ERROR on powerpc/next] [also build test ERROR on v4.13-rc3 next-20170804] [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/Hari-Bathini/powerpc-prom-avoid-endian-conversions-for-linux-memory-limit-node/20170804-060315 base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next config: powerpc-mpc836x_rdk_defconfig (attached as .config) compiler: powerpc-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705 reproduce: wget https://raw.githubusercontent.com/01org/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/Hari-Bathini/powerpc-prom-avoid-endian-conversions-for-linux-memory-limit-node/20170804-060315 HEAD 10b214586e70ec6cd64fea14d0e0997cf74a6fea builds fine. It only hurts bisectibility. All errors (new ones prefixed by >>): >> arch/powerpc/kernel/prom_init.c:600:13: error: 'is_substring_param' defined >> but not used [-Werror=unused-function] static bool is_substring_param(const char *cmdline, const char *str) ^~~~~~~~~~~~~~~~~~ cc1: all warnings being treated as errors vim +/is_substring_param +600 arch/powerpc/kernel/prom_init.c 595 596 /* 597 * Check if str is a suffix of another param as "mem=" could 598 * be "iomem=" as well. 599 */ > 600 static bool is_substring_param(const char *cmdline, const char *str) 601 { 602 char *p; 603 bool ret = false; 604 605 if (cmdline == str) 606 ret = true; 607 else { 608 p = (char *)(str - 1); 609 if (*p == ' ' || *p == '"') 610 ret = true; 611 } 612 613 return ret; 614 } 615 --- 0-DAY kernel test infrastructure Open Source Technology Center https://lists.01.org/pipermail/kbuild-all Intel Corporation
.config.gz
Description: application/gzip
