From: "Philippe Mathieu-Daudé via" <qemu-devel@nongnu.org>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Michael Tokarev" <mjt@tls.msk.ru>,
"Thomas Huth" <thuth@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: [PATCH v5 0/7] tests: Refresh lcitool submodule & remove libxml2
Date: Fri, 21 Jan 2022 14:02:15 +0100 [thread overview]
Message-ID: <20220121130222.302540-1-f4bug@amsat.org> (raw)
Series fully reviewed.
Refresh lcitool to latest and remove libxml2 (mjt).
v5:
- update scripts/meson-buildoptions.sh (thuth)
- squash libvirt-ci updates (thuth)
v4:
- Fixed typos and cleaned checkpatch.pl (thuth)
- Corrected libvirt-ci submodule URL
v3:
- fix 'refresh' helper to update cirrus-ci files (danpb)
v2:
- rebased (testing/next)
- include mjt's libxml2 removal patch
Michael Tokarev (1):
drop libxml2 checks since libxml is not actually used (for parallels)
Philippe Mathieu-Daudé (6):
MAINTAINERS: Cover lcitool submodule with build test / automation
gitmodules: Correct libvirt-ci submodule URL
tests/lcitool: Include local qemu.yml when refreshing cirrus-ci files
tests/lcitool: Refresh submodule and remove libxml2
tests: Manually remove libxml2 on MSYS2 runners
tests/lcitool: Install libibumad to cover RDMA on Debian based distros
meson.build | 6 ------
.cirrus.yml | 1 -
.gitlab-ci.d/cirrus/freebsd-12.vars | 2 +-
.gitlab-ci.d/cirrus/freebsd-13.vars | 2 +-
.gitlab-ci.d/cirrus/macos-11.vars | 2 +-
.gitlab-ci.d/windows.yml | 2 --
.gitmodules | 2 +-
MAINTAINERS | 1 +
block/meson.build | 3 +--
meson_options.txt | 2 --
scripts/checkpatch.pl | 1 -
scripts/ci/org.centos/stream/8/x86_64/configure | 1 -
scripts/coverity-scan/coverity-scan.docker | 1 -
scripts/coverity-scan/run-coverity-scan | 2 +-
scripts/meson-buildoptions.sh | 3 ---
tests/docker/dockerfiles/alpine.docker | 4 ++--
tests/docker/dockerfiles/centos8.docker | 4 +---
tests/docker/dockerfiles/fedora.docker | 4 +---
tests/docker/dockerfiles/opensuse-leap.docker | 3 +--
tests/docker/dockerfiles/ubuntu1804.docker | 4 ++--
tests/docker/dockerfiles/ubuntu2004.docker | 4 ++--
tests/lcitool/libvirt-ci | 2 +-
tests/lcitool/projects/qemu.yml | 2 +-
tests/lcitool/refresh | 2 +-
24 files changed, 19 insertions(+), 41 deletions(-)
--
2.34.1
next reply other threads:[~2022-01-21 13:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 13:02 Philippe Mathieu-Daudé via [this message]
2022-01-21 13:02 ` [PATCH v5 1/7] MAINTAINERS: Cover lcitool submodule with build test / automation Philippe Mathieu-Daudé via
2022-01-21 13:02 ` [PATCH v5 2/7] gitmodules: Correct libvirt-ci submodule URL Philippe Mathieu-Daudé via
2022-01-21 13:02 ` [PATCH v5 3/7] tests/lcitool: Include local qemu.yml when refreshing cirrus-ci files Philippe Mathieu-Daudé via
2022-01-21 13:02 ` [PATCH v5 4/7] drop libxml2 checks since libxml is not actually used (for parallels) Philippe Mathieu-Daudé via
2022-01-21 13:02 ` [PATCH v5 5/7] tests/lcitool: Refresh submodule and remove libxml2 Philippe Mathieu-Daudé via
2022-01-21 13:02 ` [PATCH v5 6/7] tests: Manually remove libxml2 on MSYS2 runners Philippe Mathieu-Daudé via
2022-01-21 13:02 ` [PATCH v5 7/7] tests/lcitool: Install libibumad to cover RDMA on Debian based distros Philippe Mathieu-Daudé via
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=20220121130222.302540-1-f4bug@amsat.org \
--to=qemu-devel@nongnu.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=mjt@tls.msk.ru \
--cc=thuth@redhat.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).