xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: [OSSTEST PATCH v4 00/11] livepatch test support
Date: Wed, 7 Jun 2017 20:50:23 -0400	[thread overview]
Message-ID: <20170608005023.GR676@char.us.oracle.com> (raw)
In-Reply-To: <1496857742-20191-1-git-send-email-ian.jackson@eu.citrix.com>

On Wed, Jun 07, 2017 at 06:48:51PM +0100, Ian Jackson wrote:
> Thanks to Konrad, who passed me his git branch under the table.
> I have tidied up some loose ends, and tested it with my xen.git
> Makefile patches.

Yeey! Thank you for taking them over.
> 
> Konrad, would you please take a look at this to make sure you don't
> think I've broken anything and that my changes look sane ?  In

They look splendid!

> particlar the patches I have marked with `#' below.
> 
>  m  01   TestSupport: target_cmd_root_status: New sub which returns return code.
>  -  02   TestSupport: target_cmd_*: Add some doc comments
>  -  03   TestSupport: target_cmd_output_root_status: New sub
>  *# 04   mfi-common: Add an enable_livepatch runvar to the Xen build jobs
>  *# 05   ts-xen-build: Build livepatches test-cases

Both Reviewed-by (albeit they have my SoB so that is kind of silly, but
eh).

>  -  06   ts-livepatch: Initial test-cases.
>  -  07   sg-run-job: Add the test-livepatch.
>  m  08   make-flight: Add livepatch build/test target in the matrix.
>  *# 09   PDU/lab: Similar to xenuse

I would ditch that one. That 'lab' thing is what I use at home and
I am OK keeping it in my local branch.

>  +  10   cs-adjust-flight: Rework runvar-build-set new value handling
>  +  11   sg-check-tested: Provide --flight option
> 
> Key:
>  m   Changed only the commit message
>  -   Very minor changes
>  *   Actual changes
>  +   Added patch (not really related, TBH)
>   #  Konrad, please review this! 

Done. I am satisfied with them.
> (All compared to Konrad's v3)
> 
> Thanks,
> Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  parent reply	other threads:[~2017-06-08  0:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-07 17:48 [OSSTEST PATCH v4 00/11] livepatch test support Ian Jackson
2017-06-07 17:48 ` [OSSTEST PATCH 01/11] TestSupport: target_cmd_root_status: New sub which returns return code Ian Jackson
2017-06-07 17:48 ` [OSSTEST PATCH 02/11] TestSupport: target_cmd_*: Add some doc comments Ian Jackson
2017-06-07 17:48 ` [OSSTEST PATCH 03/11] TestSupport: target_cmd_output_root_status: New sub Ian Jackson
2017-06-07 17:48 ` [OSSTEST PATCH 04/11] mfi-common: Add an enable_livepatch runvar to the Xen build jobs Ian Jackson
2017-06-07 17:48 ` [OSSTEST PATCH 05/11] ts-xen-build: Build livepatches test-cases Ian Jackson
2017-06-07 17:48 ` [OSSTEST PATCH 06/11] ts-livepatch: Initial test-cases Ian Jackson
2017-06-07 17:48 ` [OSSTEST PATCH 07/11] sg-run-job: Add the test-livepatch Ian Jackson
2017-06-07 17:48 ` [OSSTEST PATCH 08/11] make-flight: Add livepatch build/test target in the matrix Ian Jackson
2017-06-07 17:49 ` [OSSTEST PATCH 09/11] PDU/lab: Similar to xenuse Ian Jackson
2017-06-07 17:49 ` [OSSTEST PATCH 10/11] cs-adjust-flight: Rework runvar-build-set new value handling Ian Jackson
2017-06-07 17:49 ` [OSSTEST PATCH 11/11] sg-check-tested: Provide --flight option Ian Jackson
2017-06-07 18:54 ` [OSSTEST PATCH v4 00/11] livepatch test support Ian Jackson
2017-06-08  0:50 ` Konrad Rzeszutek Wilk [this message]
2017-06-09 11:01   ` Ian Jackson
2017-06-11  0:19     ` Konrad Rzeszutek Wilk
2017-06-09 14:35   ` Ian Jackson

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=20170608005023.GR676@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).