From: Stefan Weil <weil@mail.berlios.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH, RFC] block: separate raw images from the file protocol
Date: Wed, 05 May 2010 17:38:41 +0200 [thread overview]
Message-ID: <4BE19101.6060303@mail.berlios.de> (raw)
In-Reply-To: <4BE16851.2040603@redhat.com>
Am 05.05.2010 14:45, schrieb Kevin Wolf:
> Am 04.05.2010 22:58, schrieb Stefan Weil:
>> This patch (commit 84a12e6648444f517055138a7d7f25a22d7e1029)
>> breaks QEMU for Win32:
>>
>> QEMU can no longer access \\.\PhysicalDrive0 - a feature I use quite
>> often.
>>
>> Found by git bisect, tested like this: qemu \\.\PhysicalDrive0
>
> Does the attached patch fix the problem?
>
> Kevin
Yes, the patch fixes the problem.
It needs a small modification to compile for non-win32 systems.
Stefan
prev parent reply other threads:[~2010-05-05 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 20:30 [Qemu-devel] [PATCH, RFC] block: separate raw images from the file protocol Christoph Hellwig
2010-04-08 9:50 ` Kevin Wolf
2010-05-04 20:58 ` Stefan Weil
2010-05-05 12:45 ` Kevin Wolf
2010-05-05 15:38 ` Stefan Weil [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=4BE19101.6060303@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=hch@lst.de \
--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).