qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Oksana Vohchana <ovoshcha@redhat.com>, qemu-devel@nongnu.org
Cc: wainersm@redhat.com, crosa@redhat.com
Subject: Re: [PATCH v3 0/2] Acceptance test: provides to use different transport for migration
Date: Tue, 4 Feb 2020 17:13:18 +0100	[thread overview]
Message-ID: <9a94c680-6e76-5ac8-45b2-74d9825e54fe@redhat.com> (raw)
In-Reply-To: <20200203111631.18796-1-ovoshcha@redhat.com>

On 2/3/20 12:16 PM, Oksana Vohchana wrote:
> This series makes refactoring to migration test and adds new tests with
> EXEC and UNIX protocols
> 
> ---
> v2:
>    - Removes unnecessary symbols and unused method
> 
> v3:
>   - Makes refactoring and split into 2 patches
>   - Provides TCP and EXEC migration
> 
> Oksana Vohchana (2):
>    Acceptance test: provides to use different transport for migration
>    Acceptance test: provides to use different transport for  migration
> 
>   tests/acceptance/migration.py | 52 +++++++++++++++++++++++++----------
>   1 file changed, 37 insertions(+), 15 deletions(-)
> 

Series applied to my python-next tree (splitting each patch in 2):
https://gitlab.com/philmd/qemu/commits/python-next



  parent reply	other threads:[~2020-02-04 16:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-03 11:16 [PATCH v3 0/2] Acceptance test: provides to use different transport for migration Oksana Vohchana
2020-02-03 11:16 ` [PATCH v3 1/2] " Oksana Vohchana
2020-02-04 14:09   ` Philippe Mathieu-Daudé
2020-02-03 11:16 ` [PATCH v3 2/2] " Oksana Vohchana
2020-02-04 14:12   ` Philippe Mathieu-Daudé
2020-02-04 15:02     ` Oksana Voshchana
2020-02-04 16:12       ` Philippe Mathieu-Daudé
2020-02-04 16:13 ` Philippe Mathieu-Daudé [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-02-03 10:52 [PATCH v3 0/2] " Oksana Vohchana

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=9a94c680-6e76-5ac8-45b2-74d9825e54fe@redhat.com \
    --to=philmd@redhat.com \
    --cc=crosa@redhat.com \
    --cc=ovoshcha@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wainersm@redhat.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 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).