From: Nico Boehr <nrb@linux.ibm.com>
To: David Hildenbrand <david@redhat.com>, qemu-devel@nongnu.org
Cc: linux-s390@vger.kernel.org, thuth@redhat.com,
richard.henderson@linaro.org
Subject: Re: [PATCH qemu] s390x: sck: load into a temporary not into in1
Date: Tue, 25 Jan 2022 15:54:52 +0100 [thread overview]
Message-ID: <c0b5e6151a330f58f6794ee4fac19e6319810613.camel@linux.ibm.com> (raw)
In-Reply-To: <9a888391-1020-89b0-65ed-5c93f2cc8642@redhat.com>
On Tue, 2022-01-25 at 14:13 +0100, David Hildenbrand wrote:
> I think you can actually just reuse in2_m2_64a, similar as we handle
> SCKC
I tried my SCK tests with your patch, it works just as well and seems
much cleaner, thanks.
Do you want to send this or should I make a v2 and add you as
Suggested-by?
next prev parent reply other threads:[~2022-01-25 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 12:29 [PATCH qemu] s390x: sck: load into a temporary not into in1 Nico Boehr
2022-01-25 13:13 ` David Hildenbrand
2022-01-25 14:54 ` Nico Boehr [this message]
2022-01-25 16:42 ` Philippe Mathieu-Daudé via
2022-01-25 16:44 ` David Hildenbrand
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=c0b5e6151a330f58f6794ee4fac19e6319810613.camel@linux.ibm.com \
--to=nrb@linux.ibm.com \
--cc=david@redhat.com \
--cc=linux-s390@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).