qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Hervé Poussineau" <hpoussin@reactos.org>
To: pbonzini@redhat.com, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 08/10] fdc: add CCR (Configuration Control Register) write register
Date: Tue, 10 Jan 2012 23:09:59 +0100	[thread overview]
Message-ID: <4F0CB737.3060104@reactos.org> (raw)

On 01/09/2012 09:09 AM, Paolo Bonzini wrote:

    This should go before patch 7, shouldn't it?

      


Yes, I can exchange patches 7 and 8.

However, in this order, only floppies other than 1.44 Mb may fail 
(depends if DSR or CCR register is used to write required rate).

I would like to have some more review before respinning (if required...)

Hervé

             reply	other threads:[~2012-01-10 22:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10 22:09 Hervé Poussineau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-01-08 20:27 [Qemu-devel] [PATCH 00/10] Misc fixes for floppy emulation Hervé Poussineau
2012-01-08 20:27 ` [Qemu-devel] [PATCH 08/10] fdc: add CCR (Configuration Control Register) write register Hervé Poussineau
2012-01-09  8:09   ` Paolo Bonzini
2012-01-11 20:30   ` Andreas Färber

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=4F0CB737.3060104@reactos.org \
    --to=hpoussin@reactos.org \
    --cc=pbonzini@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).