From: Paolo Bonzini <pbonzini@redhat.com>
To: marcandre.lureau@redhat.com, qemu-devel@nongnu.org
Cc: "Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-rust@nongnu.org
Subject: Re: [PATCH 1/4] rust: run cargo update
Date: Tue, 26 Aug 2025 19:43:49 +0200 [thread overview]
Message-ID: <5da180f5-1601-4022-925f-cc0669270f5e@redhat.com> (raw)
In-Reply-To: <20250826133132.4064478-2-marcandre.lureau@redhat.com>
On 8/26/25 15:31, marcandre.lureau@redhat.com wrote:
> From: Marc-André Lureau <marcandre.lureau@redhat.com>
>
> Usually, rust projects have CI bots to do that and check that nothing
> breaks. We should add this to our TODO list.
You have to adjust the subprojects as well to keep them in sync. :(
I was going to wait until Meson does it for us via cargo subprojects, or
do it as needed until then; for example I have lying around a patch to
update proc_macro2 and syn, because some experiments I did needed a
newer version.
I am applying
https://lore.kernel.org/qemu-devel/20250717062727.305466-2-pbonzini@redhat.com/
and your patch 4.
Paolo
next prev parent reply other threads:[~2025-08-26 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 13:31 [PATCH 0/4] rust: little clean-ups and updates marcandre.lureau
2025-08-26 13:31 ` [PATCH 1/4] rust: run cargo update marcandre.lureau
2025-08-26 17:43 ` Paolo Bonzini [this message]
2025-08-26 13:31 ` [PATCH 2/4] rust: remove unused global qemu "allocator" marcandre.lureau
2025-08-26 13:31 ` [PATCH 3/4] build-sys/rust: update syn to v2.0.106 marcandre.lureau
2025-08-26 13:31 ` [PATCH 4/4] rust/qemu-api-macros: make derive(Object) friendly when missing parent marcandre.lureau
2025-08-27 2:58 ` Zhao Liu
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=5da180f5-1601-4022-925f-cc0669270f5e@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=manos.pitsidianakis@linaro.org \
--cc=marcandre.lureau@redhat.com \
--cc=philmd@linaro.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).