Hi, On Tue, Feb 25, 2020 at 10:52:55AM +0800, kbuild test robot wrote: > Thank you for the patch! Yet something to improve: And thanks for the report, i will try to improve :) > [auto build test ERROR on tip/timers/core] > [also build test ERROR on arm-soc/for-next powerpc/next linus/master v5.6-rc3 next-20200221] > [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] i did use --base option w/ git format-patch, though the output of it was rigged to indicate a human understandable start point that can be parsed by the script as well. In cover letter, there was "base-commit: v5.6-rc1", test robot cannot make use of that information ?, since my thought was that your script would create a branch with any valid start point following "base-commit:" > drivers/clocksource/timer-prima2.c: In function 'sirfsoc_prima2_timer_init': > >> drivers/clocksource/timer-prima2.c:213:2: error: 'sirfsoc_timer_irq' undeclared (first use in this function); did you mean 'sirfsoc_timer_read'? > sirfsoc_timer_irq.irq = irq_of_parse_and_map(np, 0); > ^~~~~~~~~~~~~~~~~ > sirfsoc_timer_read > drivers/clocksource/timer-prima2.c:213:2: note: each undeclared identifier is reported only once for each function it appears in Does the robot keep the log of patches that are successfully built ?, w/ v1, i did not receive similar report, and tried to find if test robot has successfully built v1, but couldn't find out. Regards afzal
