From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: [PULL 0/1] HVF fix QEMU 4.2-rc
Date: Tue, 3 Dec 2019 09:12:58 +0100 [thread overview]
Message-ID: <20191203081259.906-1-pbonzini@redhat.com> (raw)
The following changes since commit 39032981fa851d25fb27527f25f046fed800e585:
Merge remote-tracking branch 'remotes/armbru/tags/pull-error-2019-12-02' into staging (2019-12-02 16:29:41 +0000)
are available in the Git repository at:
git://github.com/bonzini/qemu.git tags/for-upstream
for you to fetch changes up to 64bef038e777208e4c35beae7f980fbd994b87eb:
hvf: correctly inject VMCS_INTR_T_HWINTR versus VMCS_INTR_T_SWINTR. (2019-12-03 09:11:42 +0100)
----------------------------------------------------------------
* last HVF fix (Cameron)
----------------------------------------------------------------
Cameron Esfahani (1):
hvf: correctly inject VMCS_INTR_T_HWINTR versus VMCS_INTR_T_SWINTR.
target/i386/hvf/hvf.c | 4 +++-
target/i386/hvf/x86hvf.c | 14 +++++++++-----
2 files changed, 12 insertions(+), 6 deletions(-)
--
2.21.0
next reply other threads:[~2019-12-03 8:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 8:12 Paolo Bonzini [this message]
2019-12-03 8:12 ` [PULL 1/1] hvf: correctly inject VMCS_INTR_T_HWINTR versus VMCS_INTR_T_SWINTR Paolo Bonzini
2019-12-03 11:03 ` [PULL 0/1] HVF fix QEMU 4.2-rc Peter Maydell
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=20191203081259.906-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).