From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>
Subject: [Qemu-devel] [PULL 0/3] pc, virtio: fixes
Date: Tue, 3 Jul 2018 02:48:08 +0300 [thread overview]
Message-ID: <20180702234631.12268-1-mst@redhat.com> (raw)
The following changes since commit 00928a421d47f49691cace1207481b7aad31b1f1:
Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20180626' into staging (2018-06-26 18:23:49 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_upstream
for you to fetch changes up to 5d9c9ea22ab4f3b3ee497523e34b6f4d3281f62d:
virtio-rng: process pending requests on DRIVER_OK (2018-06-28 04:46:16 +0300)
----------------------------------------------------------------
pc, virtio: fixes
A couple of fixes to amd iommu, and a fix to virtio iommu.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
----------------------------------------------------------------
Jan Kiszka (2):
hw/i386: Fix IVHD entry length for AMD IOMMU
hw/i386: Fix AMDVI GATS and HATS encodings
Pankaj Gupta (1):
virtio-rng: process pending requests on DRIVER_OK
hw/i386/amd_iommu.h | 4 ++--
hw/i386/acpi-build.c | 2 +-
hw/virtio/virtio-rng.c | 14 ++++++++++++++
3 files changed, 17 insertions(+), 3 deletions(-)
next reply other threads:[~2018-07-02 23:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 23:48 Michael S. Tsirkin [this message]
2018-07-02 23:48 ` [Qemu-devel] [PULL 1/3] hw/i386: Fix IVHD entry length for AMD IOMMU Michael S. Tsirkin
2018-07-02 23:48 ` [Qemu-devel] [PULL 2/3] hw/i386: Fix AMDVI GATS and HATS encodings Michael S. Tsirkin
2018-07-02 23:48 ` [Qemu-devel] [PULL 3/3] virtio-rng: process pending requests on DRIVER_OK Michael S. Tsirkin
2018-07-03 9:46 ` [Qemu-devel] [PULL 0/3] pc, virtio: fixes 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=20180702234631.12268-1-mst@redhat.com \
--to=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--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).