From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Anthony Liguori <aliguori@amazon.com>
Subject: [Qemu-devel] [PULL 0/5] acpi,pc,pci,virtio,memory bug fixes
Date: Mon, 17 Feb 2014 16:25:23 +0200 [thread overview]
Message-ID: <1392647087-23020-1-git-send-email-mst@redhat.com> (raw)
The following changes since commit 417c45ab2f847c0a47b1232f611aa886df6a97d5:
ACPI: Remove commented-out code from HPET._CRS (2014-02-10 11:09:33 +0200)
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 0217598857eaf0ceae137cdd71445118af2284cf:
PCIE: fix regression with coldplugged multifunction device (2014-02-17 16:17:31 +0200)
----------------------------------------------------------------
acpi,pc,pci,virtio,memory bug fixes
This collects several small fixes from all over the place.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
----------------------------------------------------------------
Igor Mammedov (2):
memory_region_present: return false if address is not found in child MemoryRegion
PCIE: fix regression with coldplugged multifunction device
Joel Stanley (1):
virtio-net: remove function calls from assert
Michael S. Tsirkin (2):
acpi-build: append description for non-hotplug
acpi-test-data: update expected files
include/exec/memory.h | 6 +-
hw/i386/acpi-build.c | 140 ++++++++++++++++++++++++++++++++++--------
hw/net/virtio-net.c | 7 ++-
hw/pci/pcie.c | 16 ++---
memory.c | 2 +-
tests/acpi-test.c | 2 +-
hw/i386/acpi-dsdt.dsl | 41 +++----------
hw/i386/q35-acpi-dsdt.dsl | 29 ++-------
hw/i386/ssdt-pcihp.dsl | 56 +++++++++++++++++
tests/acpi-test-data/pc/DSDT | Bin 4582 -> 4461 bytes
tests/acpi-test-data/pc/SSDT | Bin 2200 -> 2299 bytes
tests/acpi-test-data/q35/DSDT | Bin 7438 -> 7370 bytes
tests/acpi-test-data/q35/SSDT | Bin 475 -> 588 bytes
13 files changed, 201 insertions(+), 98 deletions(-)
next reply other threads:[~2014-02-17 14:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 14:25 Michael S. Tsirkin [this message]
2014-02-17 14:25 ` [Qemu-devel] [PULL 1/5] acpi-build: append description for non-hotplug Michael S. Tsirkin
2014-02-17 14:51 ` Gabriel L. Somlo
2014-02-17 16:44 ` Michael S. Tsirkin
2014-02-19 13:52 ` Peter Maydell
2014-02-19 14:36 ` Michael S. Tsirkin
2014-02-19 13:50 ` Michael S. Tsirkin
2014-02-19 15:24 ` Gabriel L. Somlo
2014-02-19 19:09 ` Michael S. Tsirkin
2014-02-19 19:02 ` Michael S. Tsirkin
2014-02-19 19:45 ` Gabriel L. Somlo
2014-02-20 5:13 ` Michael S. Tsirkin
2014-02-20 14:22 ` Gabriel L. Somlo
2014-02-20 15:29 ` Michael S. Tsirkin
2014-02-19 16:09 ` Alex Williamson
2014-02-17 14:25 ` [Qemu-devel] [PULL 2/5] acpi-test-data: update expected files Michael S. Tsirkin
2014-02-17 14:25 ` [Qemu-devel] [PULL 3/5] virtio-net: remove function calls from assert Michael S. Tsirkin
2014-02-17 14:25 ` [Qemu-devel] [PULL 4/5] memory_region_present: return false if address is not found in child MemoryRegion Michael S. Tsirkin
2014-02-17 14:25 ` [Qemu-devel] [PULL 5/5] PCIE: fix regression with coldplugged multifunction device Michael S. Tsirkin
2014-02-19 14:35 ` [Qemu-devel] [PULL 0/5] acpi,pc,pci,virtio,memory bug 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=1392647087-23020-1-git-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=aliguori@amazon.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).