From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: linux-cxl@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
qemu-arm@nongnu.org, "Junjie Cao" <junjie.cao@intel.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Anisa Su" <anisa.su@samsung.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PATCH v2 0/2] hw/pci-bridge: fix build with CONFIG_CXL disabled
Date: Mon, 28 Sep 2026 10:56:44 +0100 [thread overview]
Message-ID: <20260928095646.3555447-1-berrange@redhat.com> (raw)
See patch 2 for the details
Changed in v2:
* Instead of using CONFIG_CXL in pci_expander_bridge.c
split the file in two and conditionalize in meson.build
Daniel P. Berrangé (2):
hw/arm: remove pci-bridge/pci_expander_bridge.h from virt.c
hw/pci-bridge: split CXL PXB into separate file
hw/arm/virt.c | 1 -
hw/cxl/cxl-host.c | 2 +-
hw/pci-bridge/meson.build | 4 +-
hw/pci-bridge/pci_expander_bridge.c | 194 +----------------
hw/pci-bridge/pci_expander_bridge_common.h | 29 +++
hw/pci-bridge/pci_expander_bridge_cxl.c | 201 ++++++++++++++++++
hw/pci-bridge/pci_expander_bridge_stubs.c | 14 --
...der_bridge.h => pci_expander_bridge_cxl.h} | 0
8 files changed, 242 insertions(+), 203 deletions(-)
create mode 100644 hw/pci-bridge/pci_expander_bridge_common.h
create mode 100644 hw/pci-bridge/pci_expander_bridge_cxl.c
delete mode 100644 hw/pci-bridge/pci_expander_bridge_stubs.c
rename include/hw/pci-bridge/{pci_expander_bridge.h => pci_expander_bridge_cxl.h} (100%)
--
2.55.0
next reply other threads:[~2026-09-28 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 9:56 Daniel P. Berrangé [this message]
2026-09-28 9:56 ` [PATCH v2 1/2] hw/arm: remove pci-bridge/pci_expander_bridge.h from virt.c Daniel P. Berrangé
2026-09-28 10:01 ` Philippe Mathieu-Daudé
2026-09-28 9:56 ` [PATCH v2 2/2] hw/pci-bridge: split CXL PXB into separate file Daniel P. Berrangé
2026-09-28 10:03 ` Philippe Mathieu-Daudé
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=20260928095646.3555447-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=anisa.su@samsung.com \
--cc=jic23@kernel.org \
--cc=junjie.cao@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@oss.qualcomm.com \
--cc=qemu-arm@nongnu.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