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] i386: Fix the missing Rust HPET configuration option
Date: Tue, 18 Feb 2025 16:40:53 +0800 [thread overview]
Message-ID: <Z7RHlbXUQuz1gfj7@intel.com> (raw)
In-Reply-To: <e43f8169-4017-4a3a-9274-4daf9919c290@redhat.com>
> The config item is already declared in rust/hw/timer/Kconfig, so it's enough
> to do
>
> diff --git b/rust/hw/timer/Kconfig a/rust/hw/timer/Kconfig
> index afd98033503..42e421317a5 100644
> --- b/rust/hw/timer/Kconfig
> +++ a/rust/hw/timer/Kconfig
> @@ -1,2 +1,3 @@
> config X_HPET_RUST
> bool
> + default y if PC && HAVE_RUST
>
> I applied it with your commit message.
>
Ah, thanks! I misunderstood your comment before...
Regards,
Zhao
prev parent reply other threads:[~2025-02-18 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 15:44 [PATCH] i386: Fix the missing Rust HPET configuration option Zhao Liu
2025-02-18 8:09 ` Paolo Bonzini
2025-02-18 8:40 ` 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=Z7RHlbXUQuz1gfj7@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).