Hi Dave,

[auto build test ERROR on v4.4-rc5]
[also build test ERROR on next-20151217]
[cannot apply to tip/x86/core]

url:    
https://github.com/0day-ci/linux/commits/Dave-Hansen/x86-pass-in-size-to-early-cmdline-parsing/20151218-060427
config: i386-allyesconfig (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   arch/x86/kernel/check.c: In function 'test_early_cmdline':
>> arch/x86/kernel/check.c:170:19: error: storage class specified for parameter 
>> '__initcall_test_early_cmdline7'
    late_initcall(test_early_cmdline);
                      ^
   arch/x86/kernel/check.c:170:1: error: parameter 
'__initcall_test_early_cmdline7' is initialized
    late_initcall(test_early_cmdline);
    ^
   arch/x86/kernel/check.c:170:1: warning: '__used__' attribute ignored 
[-Wattributes]
>> arch/x86/kernel/check.c:170:19: error: section attribute not allowed for 
>> '__initcall_test_early_cmdline7'
    late_initcall(test_early_cmdline);
                      ^
   arch/x86/kernel/check.c:170:152: error: expected declaration specifiers 
before ';' token
   arch/x86/kernel/check.c:169:5: error: old-style parameter declarations in 
prototyped function definition
    int test_early_cmdline(void)
        ^
   arch/x86/kernel/check.c:170:152: error: expected '{' at end of input
   arch/x86/kernel/check.c:170:152: warning: control reaches end of non-void 
function [-Wreturn-type]

vim +/__initcall_test_early_cmdline7 +170 arch/x86/kernel/check.c

   164          return 0;
   165  }
   166  device_initcall(start_periodic_check_for_corruption);
   167  
   168  #ifdef CONFIG_X86_TEST_EARLY_CMDLINE
   169  int test_early_cmdline(void)
 > 170  late_initcall(test_early_cmdline);
   171  #endif /* CONFIG_X86_TEST_EARLY_CMDLINE */

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

Attachment: .config.gz
Description: Binary data

Reply via email to