From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: [PULL 00/12] (Mostly) build system patches for 2023-05-26
Date: Fri, 26 May 2023 18:08:12 +0200 [thread overview]
Message-ID: <20230526160824.655279-1-pbonzini@redhat.com> (raw)
The following changes since commit a3cb6d5004ff638aefe686ecd540718a793bd1b1:
Merge tag 'pull-tcg-20230525' of https://gitlab.com/rth7680/qemu into staging (2023-05-25 11:11:52 -0700)
are available in the Git repository at:
https://gitlab.com/bonzini/qemu.git tags/for-upstream
for you to fetch changes up to b17bbf835c8998e93fd99b06164f1d63843fe8c9:
configure: ignore --make (2023-05-26 12:36:20 +0200)
----------------------------------------------------------------
* build system fixes and cleanups
* use subproject() for the dtc and keycodemapdb submodules
* fix virtio memory leak
* update slirp.wrap to latest commit in the master branch
----------------------------------------------------------------
Fabiano Rosas (2):
meson: Remove leftover comment
meson: Add static glib dependency for initrd-stress.img
Paolo Bonzini (10):
tests/docker: simplify HOST_ARCH definition
tests/vm: fix and simplify HOST_ARCH definition
Makefile: remove $(TESTS_PYTHON)
configure: unset harmful environment variables
slirp: update wrap to latest master
virtio: qmp: fix memory leak
meson: simplify logic for -Dfdt
meson: use subproject for internal libfdt
meson: use subproject for keycodemapdb
configure: ignore --make
.gitmodules | 8 +++---
configure | 29 +++++----------------
hw/virtio/virtio-qmp.c | 11 ++++----
meson.build | 54 ++++++++++++++--------------------------
scripts/archive-source.sh | 2 +-
dtc => subprojects/dtc | 0
{ui => subprojects}/keycodemapdb | 0
subprojects/slirp.wrap | 2 +-
tests/Makefile.include | 8 +++---
tests/docker/Makefile.include | 2 +-
tests/migration/meson.build | 4 ++-
tests/vm/Makefile.include | 7 +++---
ui/meson.build | 8 +++---
13 files changed, 50 insertions(+), 85 deletions(-)
rename dtc => subprojects/dtc (100%)
rename {ui => subprojects}/keycodemapdb (100%)
--
2.40.1
next reply other threads:[~2023-05-26 16:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 16:08 Paolo Bonzini [this message]
2023-05-26 16:08 ` [PULL 01/12] tests/docker: simplify HOST_ARCH definition Paolo Bonzini
2023-05-26 16:08 ` [PULL 02/12] tests/vm: fix and " Paolo Bonzini
2023-05-26 16:08 ` [PULL 03/12] Makefile: remove $(TESTS_PYTHON) Paolo Bonzini
2023-05-26 16:08 ` [PULL 04/12] configure: unset harmful environment variables Paolo Bonzini
2023-05-27 15:57 ` Michael Tokarev
2023-05-28 18:11 ` Juan Quintela
2023-05-26 16:08 ` [PULL 05/12] meson: Remove leftover comment Paolo Bonzini
2023-05-26 16:08 ` [PULL 06/12] meson: Add static glib dependency for initrd-stress.img Paolo Bonzini
2023-05-26 16:08 ` [PULL 07/12] slirp: update wrap to latest master Paolo Bonzini
2023-05-26 16:08 ` [PULL 08/12] virtio: qmp: fix memory leak Paolo Bonzini
2023-05-27 9:30 ` Michael Tokarev
2023-05-26 16:08 ` [PULL 09/12] meson: simplify logic for -Dfdt Paolo Bonzini
2023-05-26 16:08 ` [PULL 10/12] meson: use subproject for internal libfdt Paolo Bonzini
2023-05-26 16:08 ` [PULL 11/12] meson: use subproject for keycodemapdb Paolo Bonzini
2023-05-26 16:08 ` [PULL 12/12] configure: ignore --make Paolo Bonzini
2023-05-27 0:16 ` [PULL 00/12] (Mostly) build system patches for 2023-05-26 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=20230526160824.655279-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--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).