From: Pavel Hrdina <phrdina@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] fdc: Fix FD_SR0_SEEK flag
Date: Wed, 05 Sep 2012 11:28:02 +0200 [thread overview]
Message-ID: <50471B22.4080808@redhat.com> (raw)
In-Reply-To: <1346752016-3569-1-git-send-email-kwolf@redhat.com>
On 09/04/2012 11:46 AM, Kevin Wolf wrote:
> Pavel, does this make sense to you? It seems to fix the NT 3.1 floppy driver.
>
> Kevin Wolf (3):
> fdc: Remove status0 parameter from fdctrl_set_fifo()
> fdc: Fix false FD_SR0_SEEK
> fdc-test: Check READ ID
>
> hw/fdc.c | 38 ++++++++++++++----------------
> tests/fdc-test.c | 68 +++++++++++++++++++++++++++++++++++++++++++++++++++++-
> 2 files changed, 85 insertions(+), 21 deletions(-)
>
Hi Kevin, yes, it make sense to me. It's definitely better now.
prev parent reply other threads:[~2012-09-05 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 9:46 [Qemu-devel] [PATCH 0/3] fdc: Fix FD_SR0_SEEK flag Kevin Wolf
2012-09-04 9:46 ` [Qemu-devel] [PATCH 1/3] fdc: Remove status0 parameter from fdctrl_set_fifo() Kevin Wolf
2012-09-04 9:46 ` [Qemu-devel] [PATCH 2/3] fdc: Fix false FD_SR0_SEEK Kevin Wolf
2012-09-06 19:17 ` Hervé Poussineau
2012-09-04 9:46 ` [Qemu-devel] [PATCH 3/3] fdc-test: Check READ ID Kevin Wolf
2012-09-05 9:28 ` Pavel Hrdina [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=50471B22.4080808@redhat.com \
--to=phrdina@redhat.com \
--cc=kwolf@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).