From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Nick Briggs" <nicholas.h.briggs@gmail.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Li Zhijian" <lizhijian@fujitsu.com>,
"Kostiantyn Kostiuk" <kkostiuk@redhat.com>,
"Peter Xu" <peterx@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Andrew Deason" <adeason@sinenomine.net>,
"Eric Blake" <eblake@redhat.com>,
"Michael Roth" <michael.roth@amd.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
qemu-arm@nongnu.org,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>
Subject: [PATCH-for-10.2 0/3] buildsys: Fix Solaris build
Date: Mon, 17 Nov 2025 21:38:31 +0100 [thread overview]
Message-ID: <20251117203834.83713-1-philmd@linaro.org> (raw)
Unfortunately Solaris OS is not tested in our CI, so it
bit-rotted. Fortunately the fixes are easy.
Philippe Mathieu-Daudé (3):
qga/commands: Include proper Solaris header for getloadavg()
migration/rdma: Check ntohll() availability with meson
target/arm/tcg: Undefine Solaris FSCALE definition as a kludge
meson.build | 4 ++++
migration/rdma.c | 4 +---
qga/commands-posix.c | 3 +++
target/arm/tcg/translate-sve.c | 3 +++
4 files changed, 11 insertions(+), 3 deletions(-)
--
2.51.0
next reply other threads:[~2025-11-17 20:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 20:38 Philippe Mathieu-Daudé [this message]
2025-11-17 20:38 ` [PATCH-for-10.2 1/3] qga/commands: Include proper Solaris header for getloadavg() Philippe Mathieu-Daudé
2025-11-18 8:07 ` Kostiantyn Kostiuk
2025-11-18 8:50 ` Richard Henderson
2025-11-17 20:38 ` [PATCH-for-10.2 2/3] migration/rdma: Check ntohll() availability with meson Philippe Mathieu-Daudé
2025-11-17 21:36 ` Peter Xu
2025-11-18 8:48 ` Richard Henderson
2025-11-17 20:38 ` [PATCH-for-10.2 3/3] target/arm/tcg: Undefine Solaris FSCALE definition as a kludge Philippe Mathieu-Daudé
2025-11-18 8:51 ` Richard Henderson
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=20251117203834.83713-1-philmd@linaro.org \
--to=philmd@linaro.org \
--cc=adeason@sinenomine.net \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=kkostiuk@redhat.com \
--cc=lizhijian@fujitsu.com \
--cc=marcandre.lureau@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=michael.roth@amd.com \
--cc=nicholas.h.briggs@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.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;
as well as URLs for NNTP newsgroup(s).