From: Laurent Vivier <laurent@vivier.eu>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Laurent Vivier <laurent@vivier.eu>
Subject: [PULL 0/7] Trivial branch for 7.2 patches
Date: Sat, 5 Nov 2022 20:52:20 +0100 [thread overview]
Message-ID: <20221105195227.354769-1-laurent@vivier.eu> (raw)
The following changes since commit 6295a58ad1b73985b9c32d184de7d2ed1fbe1774:
Merge tag 'pull-target-arm-20221104' of https://git.linaro.org/people/pmaydell/qemu-arm into staging (2022-11-04 11:01:17 -0400)
are available in the Git repository at:
https://gitlab.com/laurent_vivier/qemu.git tags/trivial-branch-for-7.2-pull-request
for you to fetch changes up to 5a820d5d07cb101752c731799a326648a5aa185a:
tests/unit: simpler variable sequence for test-io-channel (2022-11-05 20:35:45 +0100)
----------------------------------------------------------------
Pull request trivial branch 20221103-v2
----------------------------------------------------------------
Alex Bennée (1):
tests/unit: simpler variable sequence for test-io-channel
Chuck Zmudzinski (1):
xen/pt: fix syntax error that causes FTBFS in some configurations
Han Han (1):
qapi: virtio: Fix the introduced version
Philippe Mathieu-Daudé (3):
target/m68k: Rename qregs.def -> qregs.h.inc
target/s390x: Rename insn-data/format.def -> insn-data/format.h.inc
target/tricore: Rename csfr.def -> csfr.h.inc
Stefan Weil (1):
Fix some typos in documentation and comments
docs/devel/testing.rst | 2 +-
docs/system/arm/cpu-features.rst | 2 +-
docs/system/loongarch/loongson3.rst | 2 +-
docs/tools/virtiofsd.rst | 2 +-
hw/xen/meson.build | 2 +-
include/exec/memory.h | 2 +-
qapi/qom.json | 2 +-
qapi/virtio.json | 34 +++++++++----------
qemu-options.hx | 10 +++---
qga/qapi-schema.json | 2 +-
target/m68k/{qregs.def => qregs.h.inc} | 0
target/m68k/translate.c | 4 +--
.../tcg/{insn-data.def => insn-data.h.inc} | 2 +-
.../{insn-format.def => insn-format.h.inc} | 0
target/s390x/tcg/translate.c | 10 +++---
target/tricore/{csfr.def => csfr.h.inc} | 0
target/tricore/translate.c | 4 +--
tests/qtest/libqtest.h | 2 +-
tests/unit/test-io-channel-command.c | 14 +++-----
19 files changed, 45 insertions(+), 51 deletions(-)
rename target/m68k/{qregs.def => qregs.h.inc} (100%)
rename target/s390x/tcg/{insn-data.def => insn-data.h.inc} (99%)
rename target/s390x/tcg/{insn-format.def => insn-format.h.inc} (100%)
rename target/tricore/{csfr.def => csfr.h.inc} (100%)
--
2.37.3
next reply other threads:[~2022-11-05 19:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 19:52 Laurent Vivier [this message]
2022-11-05 19:52 ` [PULL 1/7] qapi: virtio: Fix the introduced version Laurent Vivier
2022-11-05 19:52 ` [PULL 2/7] Fix some typos in documentation and comments Laurent Vivier
2022-11-05 19:52 ` [PULL 3/7] xen/pt: fix syntax error that causes FTBFS in some configurations Laurent Vivier
2022-11-05 19:52 ` [PULL 4/7] target/m68k: Rename qregs.def -> qregs.h.inc Laurent Vivier
2022-11-05 19:52 ` [PULL 5/7] target/s390x: Rename insn-data/format.def -> insn-data/format.h.inc Laurent Vivier
2022-11-05 19:52 ` [PULL 6/7] target/tricore: Rename csfr.def -> csfr.h.inc Laurent Vivier
2022-11-05 19:52 ` [PULL 7/7] tests/unit: simpler variable sequence for test-io-channel Laurent Vivier
2022-11-07 20:03 ` [PULL 0/7] Trivial branch for 7.2 patches Stefan Hajnoczi
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=20221105195227.354769-1-laurent@vivier.eu \
--to=laurent@vivier.eu \
--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).