From: Janosch Frank <frankja@linux.ibm.com>
To: Nina Schoetterl-Glausch <nsg@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Nico Boehr <nrb@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, David Hildenbrand <david@redhat.com>,
Andrew Jones <andrew.jones@linux.dev>,
kvm@vger.kernel.org, Thomas Huth <thuth@redhat.com>
Subject: Re: [kvm-unit-tests PATCH v2 2/5] s390x: lib: Remove double include
Date: Wed, 31 Jan 2024 10:04:44 +0100 [thread overview]
Message-ID: <9b1b39cb-655b-4ee5-9a64-64cf45678cde@linux.ibm.com> (raw)
In-Reply-To: <20240105225419.2841310-3-nsg@linux.ibm.com>
On 1/5/24 23:54, Nina Schoetterl-Glausch wrote:
> libcflat.h was included twice.
>
> Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> Signed-off-by: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
next prev parent reply other threads:[~2024-01-31 9:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 22:54 [kvm-unit-tests PATCH v2 0/5] s390x: STFLE nested interpretation Nina Schoetterl-Glausch
2024-01-05 22:54 ` [kvm-unit-tests PATCH v2 1/5] lib: Add pseudo random functions Nina Schoetterl-Glausch
2024-01-08 9:02 ` Andrew Jones
2024-01-05 22:54 ` [kvm-unit-tests PATCH v2 2/5] s390x: lib: Remove double include Nina Schoetterl-Glausch
2024-01-31 9:04 ` Janosch Frank [this message]
2024-01-05 22:54 ` [kvm-unit-tests PATCH v2 3/5] s390x: Add library functions for exiting from snippet Nina Schoetterl-Glausch
2024-01-08 12:47 ` Janosch Frank
2024-01-08 12:58 ` Nina Schoetterl-Glausch
2024-01-08 13:33 ` Janosch Frank
2024-01-05 22:54 ` [kvm-unit-tests PATCH v2 4/5] s390x: Use library functions for snippet exit Nina Schoetterl-Glausch
2024-01-05 22:54 ` [kvm-unit-tests PATCH v2 5/5] s390x: Add test for STFLE interpretive execution (format-0) Nina Schoetterl-Glausch
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=9b1b39cb-655b-4ee5-9a64-64cf45678cde@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=andrew.jones@linux.dev \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=nsg@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