From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Bernhard Beschow <shentey@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH] vl, pc: turn -no-fd-bootchk into a machine property
Date: Wed, 21 Feb 2024 18:34:21 +0100 [thread overview]
Message-ID: <1ce84d4b-876a-4f9c-a4b6-3bfd2f30d378@linaro.org> (raw)
In-Reply-To: <1A0875D0-5135-4F16-A252-BC9EBA9C567B@gmail.com>
On 21/2/24 10:47, Bernhard Beschow wrote:
> Great! I'll rebase my PC initialization series on top of Peter's reset cleanup series which probably results in folding cmos initialization into pc.c.
Don't, already done.
prev parent reply other threads:[~2024-02-21 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 15:53 [PATCH] vl, pc: turn -no-fd-bootchk into a machine property Paolo Bonzini
2024-02-20 18:58 ` Philippe Mathieu-Daudé
2024-02-20 22:43 ` Bernhard Beschow
2024-02-21 9:04 ` Paolo Bonzini
2024-02-21 9:47 ` Bernhard Beschow
2024-02-21 17:34 ` Philippe Mathieu-Daudé [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=1ce84d4b-876a-4f9c-a4b6-3bfd2f30d378@linaro.org \
--to=philmd@linaro.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=shentey@gmail.com \
/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).