From: Laszlo Ersek <lersek@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>, qemu-devel@nongnu.org
Cc: "Ján Tomko" <jtomko@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] q35: Re-enable FDC on pc-q35-2.3 and older
Date: Thu, 18 Jun 2015 19:50:35 +0200 [thread overview]
Message-ID: <558304EB.8000106@redhat.com> (raw)
In-Reply-To: <1434646168-3100-1-git-send-email-ehabkost@redhat.com>
On 06/18/15 18:49, Eduardo Habkost wrote:
> commit ea96bc629cbd52be98b2967a4b4f72e91dfc3ee4 doesn't match the patch
> submitted by Laszlo to qemu-devel. We reuse pc_q35_2_4_machine_options()
> inside pc_q35_2_3_machine_options(), so we need to undo the no_floppy
> change in pc_q35_2_3_machine_options().
>
> This restores the previous behavior where all the 2.3 and older machines
> had no_floppy=0.
>
> Reported-by: Ján Tomko <jtomko@redhat.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> ---
> hw/i386/pc_q35.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/hw/i386/pc_q35.c b/hw/i386/pc_q35.c
> index b68263d..082cd93 100644
> --- a/hw/i386/pc_q35.c
> +++ b/hw/i386/pc_q35.c
> @@ -403,6 +403,7 @@ DEFINE_Q35_MACHINE(v2_4, "pc-q35-2.4", NULL,
> static void pc_q35_2_3_machine_options(MachineClass *m)
> {
> pc_q35_2_4_machine_options(m);
> + m->no_floppy = 0;
> m->alias = NULL;
> SET_MACHINE_COMPAT(m, PC_COMPAT_2_3);
> }
>
Looks good to me, thanks! In fact I'm just learning that under the new
"machine type knobs" infrastructure, it's idiomatic to override settings
(ie. to assign the same field several times). Resetting m->alias to NULL
is an example.
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Cheers
Laszlo
next prev parent reply other threads:[~2015-06-18 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 16:49 [Qemu-devel] [PATCH] q35: Re-enable FDC on pc-q35-2.3 and older Eduardo Habkost
2015-06-18 17:50 ` Laszlo Ersek [this message]
2015-06-19 6:43 ` Markus Armbruster
2015-06-19 9:33 ` Peter Maydell
2015-06-19 15:49 ` Eduardo Habkost
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=558304EB.8000106@redhat.com \
--to=lersek@redhat.com \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jtomko@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@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).