From: Janosch Frank <frankja@linux.ibm.com>
To: Steffen Eiden <seiden@linux.ibm.com>,
Thomas Huth <thuth@redhat.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
David Hildenbrand <david@redhat.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH v5 4/6] s390x: uv-guest: Remove double report_prefix_pop
Date: Wed, 4 May 2022 10:38:41 +0200 [thread overview]
Message-ID: <d80270fe-e0a2-d6c3-8638-54881fe05d8a@linux.ibm.com> (raw)
In-Reply-To: <20220502093925.4118-5-seiden@linux.ibm.com>
On 5/2/22 11:39, Steffen Eiden wrote:
> Signed-off-by: Steffen Eiden <seiden@linux.ibm.com>
Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
> ---
> s390x/uv-guest.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/s390x/uv-guest.c b/s390x/uv-guest.c
> index 728c60aa..fd2cfef1 100644
> --- a/s390x/uv-guest.c
> +++ b/s390x/uv-guest.c
> @@ -111,8 +111,6 @@ static void test_sharing(void)
> cc = uv_call(0, (u64)&uvcb);
> report(cc == 0 && uvcb.header.rc == UVC_RC_EXECUTED, "unshare");
> report_prefix_pop();
> -
> - report_prefix_pop();
> }
>
> static struct {
next prev parent reply other threads:[~2022-05-04 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 9:39 [kvm-unit-tests PATCH v5 0/6] s390x: Attestation tests Steffen Eiden
2022-05-02 9:39 ` [kvm-unit-tests PATCH v5 1/6] s390x: uv-host: Add invalid command attestation check Steffen Eiden
2022-05-02 9:39 ` [kvm-unit-tests PATCH v5 2/6] s390x: lib: Add QUI getter Steffen Eiden
2022-05-02 9:39 ` [kvm-unit-tests PATCH v5 3/6] s390x: uv-guest: remove duplicated checks Steffen Eiden
2022-05-02 9:39 ` [kvm-unit-tests PATCH v5 4/6] s390x: uv-guest: Remove double report_prefix_pop Steffen Eiden
2022-05-04 8:38 ` Janosch Frank [this message]
2022-05-02 9:39 ` [kvm-unit-tests PATCH v5 5/6] s390x: uv-guest: add share bit test Steffen Eiden
2022-05-04 8:39 ` Janosch Frank
2022-05-02 9:39 ` [kvm-unit-tests PATCH v5 6/6] s390x: Add attestation tests Steffen Eiden
2022-05-04 8:36 ` Janosch Frank
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=d80270fe-e0a2-d6c3-8638-54881fe05d8a@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=seiden@linux.ibm.com \
--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