From: Martin Kletzander <mkletzan@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org,
Manos Pitsidianakis <manos.pitsidianakis@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-rust@nongnu.org, Hanna Reitz <hreitz@redhat.com>,
Kevin Wolf <kwolf@redhat.com>
Subject: [PATCH 0/2] Few fixes I found when building QEMU with Rust
Date: Fri, 1 Aug 2025 16:59:48 +0200 [thread overview]
Message-ID: <cover.1754060086.git.mkletzan@redhat.com> (raw)
I'm fairly sure the first one is alright, but I must admit I have no idea why is
the second patch needed on my system.
For both patches, please take them with a grain of salt and feel free to prove
me wrong with anything.
This used to be a bigger series until I rebased on top of Paolo's rust-next
branch and basically got half of it for free. That's why these unrelated
patches are bundled in a "series".
Martin Kletzander (2):
rust: Add antoher variant for impl_vmstate_struct! macro
tests/qemu-iotests: Indent expected error messages
rust/qemu-api/src/vmstate.rs | 11 +++++++++++
rust/qemu-api/tests/vmstate_tests.rs | 1 +
tests/qemu-iotests/039.out | 10 +++++-----
tests/qemu-iotests/061.out | 4 ++--
tests/qemu-iotests/137.out | 2 +-
5 files changed, 20 insertions(+), 8 deletions(-)
--
2.50.1
next reply other threads:[~2025-08-01 17:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-01 14:59 Martin Kletzander [this message]
2025-08-01 14:59 ` [PATCH 1/2] rust: Add antoher variant for impl_vmstate_struct! macro Martin Kletzander
2025-08-01 21:44 ` Paolo Bonzini
2025-08-04 8:56 ` Martin Kletzander
2025-08-04 10:08 ` Paolo Bonzini
2025-08-04 12:04 ` Martin Kletzander
2025-08-04 13:06 ` Paolo Bonzini
2025-08-01 14:59 ` [PATCH 2/2] tests/qemu-iotests: Indent expected error messages Martin Kletzander
2025-08-01 15:48 ` Daniel P. Berrangé
2025-08-01 19:09 ` Fabiano Rosas
2025-08-04 8:20 ` Martin Kletzander
2025-08-04 11:33 ` Kevin Wolf
2025-08-06 6:54 ` Dr. Werner Fink
2025-08-11 9:05 ` Martin Kletzander
2025-08-12 15:35 ` Kevin Wolf
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=cover.1754060086.git.mkletzan@redhat.com \
--to=mkletzan@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=manos.pitsidianakis@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-rust@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).