On Mon, Apr 3, 2017 at 2:06 PM, Fengguang Wu <lkp@xxxxxxxxx> wrote: > On Mon, Apr 03, 2017 at 12:26:54PM +0300, Andy Shevchenko wrote: >> On Mon, Apr 3, 2017 at 12:20 PM, Lee Jones <lee.jones@xxxxxxxxxx> wrote: >>> On Sun, 02 Apr 2017, Andy Shevchenko wrote: >>>> On Sun, Apr 2, 2017 at 11:03 PM, kbuild test robot <lkp@xxxxxxxxx> >>>> wrote: >>>> > Hi Andy, >>>> > >>>> > [auto build test ERROR on ljones-mfd/for-mfd-next] >>>> > [also build test ERROR on v4.11-rc4 next-20170331] >>>> > [if your patch is applied to the wrong git tree, please drop us a note >>>> > to help improve the system] >>>> >>>> Thank you for report, though... >>>> ...I doubt how below is related to my patch. This is obvious x86 code >>>> which was initially submitted without >>>> depend on X86 >>>> line in corresponding Kconfig. >>> >>> >>> I think you should probably specify the architecture in the Kconfig >>> entry, or else some `randconfig`s will fail. >> >> >> Yes, I understand how to fix this, though it's not a problem of this >> patch per se. >> >> Fengguang, is there any possible way to determine the relation between >> an error and a root cause change? > > > Andy, our 0day build error reports are all bisected ones. It means the > error happens since the reported patch/commit, which is either > responsible for the root cause, or somehow triggers (or changes the > exact form of) an old bug. Thanks, like you said in this case it looks pretty much for triggering an old bug. -- With Best Regards, Andy Shevchenko -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
