From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Janosch Frank <frankja@linux.vnet.ibm.com>,
KVM <kvm@vger.kernel.org>, David Hildenbrand <david@redhat.com>,
Thomas Huth <thuth@redhat.com>,
linux-s390 <linux-s390@vger.kernel.org>,
Vasily Gorbik <gor@linux.ibm.com>
Subject: Re: [PATCH 0/1] s390/uv: fix for ultravisor query function
Date: Mon, 10 Feb 2020 18:32:49 +0100 [thread overview]
Message-ID: <20200210183249.7816e316.cohuck@redhat.com> (raw)
In-Reply-To: <20200210165439.3767-1-borntraeger@de.ibm.com>
On Mon, 10 Feb 2020 11:54:38 -0500
Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> As outlined by the architects the query command could actually return more
> than the minimal 168 bytes.
>
> I will carry this with the KVM host support for protected virtualization
As this is cc:stable (and also relevant for the guest side), why not
merge it right now?
>
> Christian Borntraeger (1):
> s390/uv: Fix handling of length extensions
>
> arch/s390/boot/uv.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
next prev parent reply other threads:[~2020-02-10 17:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 16:54 [PATCH 0/1] s390/uv: fix for ultravisor query function Christian Borntraeger
2020-02-10 16:54 ` [PATCH 1/1] s390/uv: Fix handling of length extensions Christian Borntraeger
2020-02-10 17:31 ` Cornelia Huck
2020-02-10 18:46 ` Christian Borntraeger
2020-02-11 8:11 ` Janosch Frank
2020-02-10 17:32 ` Cornelia Huck [this message]
2020-02-10 17:35 ` [PATCH 0/1] s390/uv: fix for ultravisor query function Christian Borntraeger
2020-02-10 18:57 ` Christian Borntraeger
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=20200210183249.7816e316.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=gor@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.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 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.