From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Marcel Apfelbaum" <marcel@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Cornelia Huck" <cohuck@redhat.com>,
"Yongbok Kim" <yongbok.kim@mips.com>
Subject: [Qemu-devel] [PULL 4/9] hw/pcie-pci-bridge: restrict to X86 and ARM
Date: Thu, 16 Nov 2017 18:40:49 +0200 [thread overview]
Message-ID: <1510850407-17266-5-git-send-email-mst@redhat.com> (raw)
In-Reply-To: <1510850407-17266-1-git-send-email-mst@redhat.com>
From: Marcel Apfelbaum <marcel@redhat.com>
The PCIE-PCI bridge is specific to "pure" PCIe systems
(on QEMU we have X86 and ARM), it does not make sense to
have it in other archs.
Reported-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Marcel Apfelbaum <marcel@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Tested-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Tested-by: Yongbok Kim <yongbok.kim@mips.com>
---
hw/pci-bridge/Makefile.objs | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/pci-bridge/Makefile.objs b/hw/pci-bridge/Makefile.objs
index 666db37..1b05023 100644
--- a/hw/pci-bridge/Makefile.objs
+++ b/hw/pci-bridge/Makefile.objs
@@ -1,5 +1,5 @@
-common-obj-y += pci_bridge_dev.o pcie_pci_bridge.o
-common-obj-$(CONFIG_PCIE_PORT) += pcie_root_port.o gen_pcie_root_port.o
+common-obj-y += pci_bridge_dev.o
+common-obj-$(CONFIG_PCIE_PORT) += pcie_root_port.o gen_pcie_root_port.o pcie_pci_bridge.o
common-obj-$(CONFIG_PXB) += pci_expander_bridge.o
common-obj-$(CONFIG_XIO3130) += xio3130_upstream.o xio3130_downstream.o
common-obj-$(CONFIG_IOH3420) += ioh3420.o
--
MST
next prev parent reply other threads:[~2017-11-16 16:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 16:40 [Qemu-devel] [PULL 0/9] pc, pci, virtio: fixes for rc1 Michael S. Tsirkin
2017-11-16 16:40 ` [Qemu-devel] [PULL 1/9] fix: unrealize virtio device if we fail to hotplug it Michael S. Tsirkin
2017-11-16 16:40 ` [Qemu-devel] [PULL 2/9] pci: Initialize pci_dev->name before use Michael S. Tsirkin
2017-11-16 16:40 ` [Qemu-devel] [PULL 3/9] hw/pci-host: Fix x86 Host Bridges 64bit PCI hole Michael S. Tsirkin
2017-11-16 16:40 ` Michael S. Tsirkin [this message]
2017-11-16 16:40 ` [Qemu-devel] [PULL 5/9] tests/acpi-test-data: update _CRS in DSDT Michael S. Tsirkin
2017-11-16 16:40 ` [Qemu-devel] [PULL 6/9] NUMA: Enable adding NUMA node implicitly Michael S. Tsirkin
2017-11-16 16:50 ` Thadeu Lima de Souza Cascardo
2017-11-16 16:41 ` [Qemu-devel] [PULL 7/9] vmcoreinfo: put it in the 'misc' device category Michael S. Tsirkin
2017-11-16 16:41 ` [Qemu-devel] [PULL 8/9] build-sys: restrict vmcoreinfo to fw_cfg+dma capable targets Michael S. Tsirkin
2017-11-16 16:41 ` [Qemu-devel] [PULL 9/9] tests/bios-tables-test: Fix endianess problems when passing data to iasl Michael S. Tsirkin
2017-11-17 9:24 ` [Qemu-devel] [PULL 0/9] pc, pci, virtio: fixes for rc1 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=1510850407-17266-5-git-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=f4bug@amsat.org \
--cc=marcel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=yongbok.kim@mips.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 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).