From: Heiko Carstens <hca@linux.ibm.com>
To: Janosch Frank <frankja@linux.ibm.com>
Cc: Eric Farman <farman@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Shuah Khan <shuah@kernel.org>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v4 0/2] KVM: s390: Fix AR parameter in ioctl
Date: Wed, 21 Feb 2024 12:26:00 +0100 [thread overview]
Message-ID: <20240221112600.7561-B-hca@linux.ibm.com> (raw)
In-Reply-To: <bbe1db67-386b-4738-83d5-6e02cd3c9d58@linux.ibm.com>
On Wed, Feb 21, 2024 at 08:49:58AM +0100, Janosch Frank wrote:
> On 2/20/24 22:12, Eric Farman wrote:
> > Hi Janosch,
> >
> > Here is a new (final?) version for the AR/MEM_OP issue I'm attempting to
> > address. Hopefully they can be picked up to whatever tree makes sense.
> >
>
> I've got good and bad news for you :)
>
> You need to re-base this patch set on Heiko's feature branch once my kvm fpu
> patch is on there since the current version runs into conflicts with Heiko's
> fpu rework. We'll contact you once that's the case. The patch made it onto
> devel yesterday evening and I assumed you'd wait a bit until sending a new
> version but I was mistaken.
I resolved the trivial merge conflict - no need to resend anything.
Series applied, thanks!
next prev parent reply other threads:[~2024-02-21 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 21:12 [PATCH v4 0/2] KVM: s390: Fix AR parameter in ioctl Eric Farman
2024-02-20 21:12 ` [PATCH v4 1/2] KVM: s390: fix access register usage in ioctls Eric Farman
2024-02-20 21:12 ` [PATCH v4 2/2] KVM: s390: selftests: memop: add a simple AR test Eric Farman
2024-02-21 7:49 ` [PATCH v4 0/2] KVM: s390: Fix AR parameter in ioctl Janosch Frank
2024-02-21 11:26 ` Heiko Carstens [this message]
2024-02-21 11:43 ` Eric Farman
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=20240221112600.7561-B-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=farman@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.org \
--cc=svens@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.