From: Zhao Liu <zhao1.liu@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-rust@nongnu.org
Subject: Re: [PATCH] rust: hide panicking default associated constants from rustdoc
Date: Mon, 8 Dec 2025 11:36:52 +0800 [thread overview]
Message-ID: <aTZH1JW+rYXNZK/E@intel.com> (raw)
In-Reply-To: <20251204105017.2564277-1-pbonzini@redhat.com>
On Thu, Dec 04, 2025 at 11:50:17AM +0100, Paolo Bonzini wrote:
> Date: Thu, 4 Dec 2025 11:50:17 +0100
> From: Paolo Bonzini <pbonzini@redhat.com>
> Subject: [PATCH] rust: hide panicking default associated constants from
> rustdoc
> X-Mailer: git-send-email 2.52.0
>
> Work around rustdoc issue that panics while trying to evaluate
> the constants.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> rust/hw/core/src/qdev.rs | 1 +
> rust/migration/src/vmstate.rs | 1 +
> 2 files changed, 2 insertions(+)
Reviewed-by: Zhao Liu <zhao1.liu@intel.com>
prev parent reply other threads:[~2025-12-08 3:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 10:50 [PATCH] rust: hide panicking default associated constants from rustdoc Paolo Bonzini
2025-12-08 3:36 ` Zhao Liu [this message]
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=aTZH1JW+rYXNZK/E@intel.com \
--to=zhao1.liu@intel.com \
--cc=pbonzini@redhat.com \
--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).