On 04/13, Joe Lawrence wrote: >On 04/13/2018 11:49 AM, Philip Li wrote: >> On Wed, Apr 11, 2018 at 09:59:59AM -0400, Joe Lawrence wrote: >>> On 04/10/2018 11:44 PM, kbuild test robot wrote: >>>> Hi Joe, >>>> >>>> Thank you for the patch! Yet something to improve: >>>> >>>> [auto build test ERROR on v4.16] >>>> [also build test ERROR on next-20180410] >>>> [cannot apply to linus/master jikos-livepatching/for-next] >>>> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] >>> ^^^^^^^^^^^^^^ >>> Hi kbuild test robot, >>> >>> Thank you for testing! Yet something to improve: >>> >>> Is there syntax one can add to a commit, or better yet, patchset cover >>> letter to specify a git tree URL in which the patch(set) is based on? >> thanks Joe, currently we recommend to use --base option when using git format-patch. >> This will record the base of your series, and 0day would act accordingly to apply >> to that base. > >I didn't know about the --base option, that looks like a cool feature. >BTW, I assume that "well-known patches" would apply to those posted to >any upstream mailing list that the kbuild test robot is currently >listening to? Yes, as 0day monitors most of maintainers' and core kernel developers' trees that contain those "well known" patches. Thanks, Xiaolong > >-- Joe >_______________________________________________ >kbuild-all mailing list >kbuild-all@xxxxxxxxxxxx >https://lists.01.org/mailman/listinfo/kbuild-all -- To unsubscribe from this list: send the line "unsubscribe live-patching" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
