From: Thomas Huth <thuth@redhat.com>
To: Jonathan Cameron <jonathan.cameron@huawei.com>, qemu-devel@nongnu.org
Cc: Fan Ni <fan.ni@samsung.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
qemu-trivial@nongnu.org
Subject: [PATCH 0/3] cxl: Fix issues with g_steal_pointer()
Date: Mon, 4 Mar 2024 11:44:03 +0100 [thread overview]
Message-ID: <20240304104406.59855-1-thuth@redhat.com> (raw)
When setting GLIB_VERSION_MAX_ALLOWED to GLIB_VERSION_2_58 or higher
(which we'll certainly do in the not too distant future), glib adds
type safety checks to the g_steal_pointer() macro. This triggers
errors in the cxl code since the pointer types do not always match
here. Let's fix those errors now so we can switch to a newer version
of the glib in a future version of QEMU.
Thomas Huth (3):
hw/cxl/cxl-cdat: Fix type of buf in ct3_load_cdat()
hw/pci-bridge/cxl_upstream: Fix problem with g_steal_pointer()
hw/mem/cxl_type3: Fix problem with g_steal_pointer()
include/hw/cxl/cxl_cdat.h | 17 +++++++++++------
hw/cxl/cxl-cdat.c | 4 ++--
hw/mem/cxl_type3.c | 24 ++++++++++++------------
hw/pci-bridge/cxl_upstream.c | 8 ++++----
4 files changed, 29 insertions(+), 24 deletions(-)
--
2.44.0
next reply other threads:[~2024-03-04 10:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 10:44 Thomas Huth [this message]
2024-03-04 10:44 ` [PATCH 1/3] hw/cxl/cxl-cdat: Fix type of buf in ct3_load_cdat() Thomas Huth
2024-03-04 14:57 ` Jonathan Cameron via
2024-03-04 10:44 ` [PATCH 2/3] hw/pci-bridge/cxl_upstream: Fix problem with g_steal_pointer() Thomas Huth
2024-03-04 15:06 ` Jonathan Cameron via
2024-03-04 15:12 ` Jonathan Cameron via
2024-03-04 10:44 ` [PATCH 3/3] hw/mem/cxl_type3: " Thomas Huth
2024-03-04 15:10 ` Jonathan Cameron via
2024-03-05 7:27 ` Thomas Huth
2024-03-05 15:52 ` Jonathan Cameron via
2024-03-08 6:14 ` [PATCH 0/3] cxl: Fix issues " Michael Tokarev
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=20240304104406.59855-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=fan.ni@samsung.com \
--cc=jonathan.cameron@huawei.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).