All of lore.kernel.org
 help / color / mirror / Atom feed
From: philip.li at intel.com (Philip Li)
Subject: [kbuild-all] [PATCH v2] selftests/livepatch: introduce tests
Date: Fri, 13 Apr 2018 23:49:01 +0800	[thread overview]
Message-ID: <20180413154901.GD20885@intel.com> (raw)
In-Reply-To: <b20ea6f4-5f8a-d99b-deaf-eb76297251a2@redhat.com>

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 can't find anything at [1] that documents such feature.
> 
> [1] https://01.org/lkp/documentation/0-day-test-service
> 
> Thanks,
> 
> -- Joe
> _______________________________________________
> kbuild-all mailing list
> kbuild-all at lists.01.org
> https://lists.01.org/mailman/listinfo/kbuild-all
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: philip.li@intel.com (Philip Li)
Subject: [kbuild-all] [PATCH v2] selftests/livepatch: introduce tests
Date: Fri, 13 Apr 2018 23:49:01 +0800	[thread overview]
Message-ID: <20180413154901.GD20885@intel.com> (raw)
Message-ID: <20180413154901.9MrheJ3mC3xGeBPVYbhauGpH-Ad1DGhQcbsMH03PhuU@z> (raw)
In-Reply-To: <b20ea6f4-5f8a-d99b-deaf-eb76297251a2@redhat.com>

On Wed, Apr 11, 2018@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 can't find anything at [1] that documents such feature.
> 
> [1] https://01.org/lkp/documentation/0-day-test-service
> 
> Thanks,
> 
> -- Joe
> _______________________________________________
> kbuild-all mailing list
> kbuild-all at lists.01.org
> https://lists.01.org/mailman/listinfo/kbuild-all
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2018-04-13 15:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-10 15:15 [PATCH v2] Add livepatch kselftests Joe Lawrence
2018-04-10 15:15 ` Joe Lawrence
2018-04-10 15:15 ` joe.lawrence
2018-04-10 15:15 ` [PATCH v2] selftests/livepatch: introduce tests Joe Lawrence
2018-04-10 15:15   ` Joe Lawrence
2018-04-10 15:15   ` joe.lawrence
2018-04-10 20:00   ` Josh Poimboeuf
2018-04-10 20:00     ` Josh Poimboeuf
2018-04-10 20:00     ` jpoimboe
2018-04-10 20:50     ` Joe Lawrence
2018-04-10 20:50       ` Joe Lawrence
2018-04-10 20:50       ` joe.lawrence
2018-04-10 21:33       ` Josh Poimboeuf
2018-04-10 21:33         ` Josh Poimboeuf
2018-04-10 21:33         ` jpoimboe
2018-04-10 21:38         ` Jiri Kosina
2018-04-10 21:38           ` Jiri Kosina
2018-04-10 21:38           ` jikos
2018-04-11  3:44   ` kbuild test robot
2018-04-11 13:59     ` joe.lawrence
2018-04-11 13:59       ` Joe Lawrence
2018-04-13 15:49       ` philip.li [this message]
2018-04-13 15:49         ` [kbuild-all] " Philip Li
2018-04-13 20:55         ` joe.lawrence
2018-04-13 20:55           ` Joe Lawrence
2018-04-17  2:32           ` xiaolong.ye
2018-04-17  2:32             ` Ye Xiaolong
2018-04-10 20:04 ` [PATCH v2] Add livepatch kselftests Josh Poimboeuf
2018-04-10 20:04   ` Josh Poimboeuf
2018-04-10 20:04   ` jpoimboe
2018-04-12 13:28 ` Miroslav Benes
2018-04-12 13:28   ` Miroslav Benes
2018-04-12 13:28   ` mbenes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180413154901.GD20885@intel.com \
    --to=unknown@example.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.