From: Kevin Wolf <kwolf@redhat.com>
To: jcody@redhat.com
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] block: add bdrv_reopen() support for raw hdev devices
Date: Mon, 19 Nov 2012 17:19:15 +0100 [thread overview]
Message-ID: <50AA5C03.4050105@redhat.com> (raw)
In-Reply-To: <50AA5B58.8080509@redhat.com>
Am 19.11.2012 17:16, schrieb Jeff Cody:
> On 11/19/2012 10:45 AM, Kevin Wolf wrote:
>> Am 19.11.2012 16:37, schrieb Jeff Cody:
>>> The host device reopen handler for raw-posix is the same as the file reopen
>>> handler.
>>>
>
>>
>> What about host_floppy and (twice) host_cdrom?
>>
>> Kevin
>>
>
> Do we need / want reopen for floppy and/or cdrom?
At least I can't see what makes it less reasonable than for host_device.
They are really just host_device with one or two additional callbacks
for handling removable media.
Kevin
prev parent reply other threads:[~2012-11-19 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 15:37 [Qemu-devel] [PATCH] block: add bdrv_reopen() support for raw hdev devices Jeff Cody
2012-11-19 15:45 ` Kevin Wolf
2012-11-19 16:16 ` Jeff Cody
2012-11-19 16:19 ` Kevin Wolf [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=50AA5C03.4050105@redhat.com \
--to=kwolf@redhat.com \
--cc=jcody@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).