qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Maxim Levitsky <mlevitsk@redhat.com>, qemu-devel@nongnu.org
Cc: "Laurent Vivier" <lvivier@redhat.com>,
	"Kevin Wolf" <kwolf@redhat.com>, "Thomas Huth" <thuth@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Eduardo Habkost" <ehabkost@redhat.com>,
	qemu-block@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH v3 0/2] Assorted fixes to tests that were broken by recent scsi changes
Date: Thu, 5 Nov 2020 10:01:34 +0100	[thread overview]
Message-ID: <e1c61887-6bc4-d1eb-97c7-0731d308b3c5@redhat.com> (raw)
In-Reply-To: <20201104185025.434703-1-mlevitsk@redhat.com>

On 04.11.20 19:50, Maxim Levitsky wrote:
> While most of the patches in V1 of this series are already merged upstream,
> the patch that fixes iotest 240 was broken on s390 and was not accepted.
> 
> This is	an updated version of this patch, based on Paulo's suggestion,
> that hopefully makes this iotest work on both x86 and s390.
> 
> V3: addressed review feedback
> 
> Best regards,
> 	Maxim Levitsky
> 
> Maxim Levitsky (2):
>    iotests: add filter_qmp_virtio_scsi function
>    iotests: rewrite iotest 240 in python
> 
>   tests/qemu-iotests/240        | 219 ++++++++++++++--------------------
>   tests/qemu-iotests/240.out    |  76 ++++++------
>   tests/qemu-iotests/iotests.py |  10 ++
>   3 files changed, 140 insertions(+), 165 deletions(-)

Thanks, applied to my block branch:

https://git.xanclic.moe/XanClic/qemu/commits/branch/block

Max



      parent reply	other threads:[~2020-11-05  9:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-04 18:50 [PATCH v3 0/2] Assorted fixes to tests that were broken by recent scsi changes Maxim Levitsky
2020-11-04 18:50 ` [PATCH v3 1/2] iotests: add filter_qmp_virtio_scsi function Maxim Levitsky
2020-11-04 18:50 ` [PATCH v3 2/2] iotests: rewrite iotest 240 in python Maxim Levitsky
2020-11-05  9:01 ` Max Reitz [this message]

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=e1c61887-6bc4-d1eb-97c7-0731d308b3c5@redhat.com \
    --to=mreitz@redhat.com \
    --cc=berrange@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=mlevitsk@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@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).