From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Maxim Levitsky <mlevitsk@redhat.com>, qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
qemu-block@nongnu.org, "Max Reitz" <mreitz@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH v2 0/2] Assorted fixes to tests that were broken by recent scsi changes
Date: Tue, 3 Nov 2020 12:57:47 +0100 [thread overview]
Message-ID: <fee407a2-4efc-3eec-0145-e03d34d79dae@de.ibm.com> (raw)
In-Reply-To: <20201101161532.259609-1-mlevitsk@redhat.com>
On 01.11.20 17:15, 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.
>
> Best regards,
> Maxim Levitsky
>
> Maxim Levitsky (2):
> iotests: add filter_qmp_virtio_scsi function
> iotests: rewrite iotest 240 in python
Both patches on s390x
Tested-by: Christian Borntraeger <borntraeger@de.ibm.com>
Thanks.
>
> tests/qemu-iotests/240 | 228 +++++++++++++++-------------------
> tests/qemu-iotests/240.out | 76 +++++++-----
> tests/qemu-iotests/iotests.py | 10 ++
> 3 files changed, 153 insertions(+), 161 deletions(-)
>
prev parent reply other threads:[~2020-11-03 11:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 16:15 [PATCH v2 0/2] Assorted fixes to tests that were broken by recent scsi changes Maxim Levitsky
2020-11-01 16:15 ` [PATCH v2 1/2] iotests: add filter_qmp_virtio_scsi function Maxim Levitsky
2020-11-01 16:15 ` [PATCH v2 2/2] iotests: rewrite iotest 240 in python Maxim Levitsky
2020-11-03 12:53 ` Max Reitz
2020-11-04 18:51 ` Maxim Levitsky
2020-11-02 8:33 ` [PATCH v2 0/2] Assorted fixes to tests that were broken by recent scsi changes Paolo Bonzini
2020-11-03 11:57 ` Christian Borntraeger [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=fee407a2-4efc-3eec-0145-e03d34d79dae@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kwolf@redhat.com \
--cc=lvivier@redhat.com \
--cc=mlevitsk@redhat.com \
--cc=mreitz@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).