From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: kvm@vger.kernel.org, linux-s390@vger.kernel.org, qemu-s390x@nongnu.org
Cc: frankja@linux.ibm.com, thuth@redhat.com
Subject: [PATCH v2 0/2] s390x: Pipeline and other minor fixes
Date: Thu, 21 Jul 2022 15:30:00 +0200 [thread overview]
Message-ID: <20220721133002.142897-1-imbrenda@linux.ibm.com> (raw)
The first patch fences a test when using TCG. When using Qemu < 7.1,
TCG would crash. This causes the CI pipeline to fail. Fence the
testcase when using TCG to get the CI pipeline to work.
The second patch adds some report_prefix_push/report_prefix_pop around
some of the new testcases to make each output line unique.
Claudio Imbrenda (2):
s390x: intercept: fence one test when using TCG
s390x: intercept: make sure all output lines are unique
s390x/intercept.c | 15 +++++++++++++--
1 file changed, 13 insertions(+), 2 deletions(-)
--
2.36.1
next reply other threads:[~2022-07-21 13:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 13:30 Claudio Imbrenda [this message]
2022-07-21 13:30 ` [PATCH v2 1/2] s390x: intercept: fence one test when using TCG Claudio Imbrenda
2022-07-21 13:41 ` Thomas Huth
2022-07-21 13:46 ` Claudio Imbrenda
2022-07-21 13:30 ` [PATCH v2 2/2] s390x: intercept: make sure all output lines are unique Claudio Imbrenda
2022-07-21 13:42 ` Thomas Huth
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=20220721133002.142897-1-imbrenda@linux.ibm.com \
--to=imbrenda@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=qemu-s390x@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