From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, KVM <kvm@vger.kernel.org>,
Cornelia Huck <cohuck@redhat.com>,
linux-s390 <linux-s390@vger.kernel.org>
Subject: Re: [GIT PULL 0/2] KVM: s390: two fixes for sthyi emulation
Date: Mon, 21 Aug 2017 18:49:51 +0200 [thread overview]
Message-ID: <20170821164951.GD17079@flask> (raw)
In-Reply-To: <1503329690-34224-1-git-send-email-borntraeger@de.ibm.com>
2017-08-21 17:34+0200, Christian Borntraeger:
> Paolo, Radim,
>
> The following changes since commit 4f899147424a189b0ad1fdd6f35784ed5a642e83:
>
> KVM: s390: take srcu lock when getting/setting storage keys (2017-07-25 14:59:52 +0200)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/kvm-s390-master-4.13-2
>
> for you to fetch changes up to 857b8de96795646c5891cf44ae6fb19b9ff74bf9:
>
> KVM: s390: sthyi: fix specification exception detection (2017-08-21 15:34:54 +0200)
>
> ----------------------------------------------------------------
> KVM: s390: two fixes for sthyi emulation
>
> - missing inline assembly constraint
> - wrong exception handling
>
> ----------------------------------------------------------------
> Heiko Carstens (2):
> KVM: s390: sthyi: fix sthyi inline assembly
> KVM: s390: sthyi: fix specification exception detection
Pulled, thanks.
prev parent reply other threads:[~2017-08-21 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 15:34 [GIT PULL 0/2] KVM: s390: two fixes for sthyi emulation Christian Borntraeger
2017-08-21 15:34 ` [GIT PULL 1/2] KVM: s390: sthyi: fix sthyi inline assembly Christian Borntraeger
2017-08-21 15:34 ` [GIT PULL 2/2] KVM: s390: sthyi: fix specification exception detection Christian Borntraeger
2017-08-21 16:49 ` Radim Krčmář [this message]
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=20170821164951.GD17079@flask \
--to=rkrcmar@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@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.