From: Kevin Wolf <kwolf@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Programmingkid <programmingkidx@gmail.com>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v3] ui/cocoa.m: Machine menu patch for Mac OS X
Date: Mon, 16 Feb 2015 11:08:21 +0100 [thread overview]
Message-ID: <20150216100821.GA4079@noname.str.redhat.com> (raw)
In-Reply-To: <CAFEAcA_CKrmO4omGo9EqEXNtS-db_DrKDnaEPefXnCKzJDS+iA@mail.gmail.com>
Am 14.02.2015 um 03:28 hat Peter Maydell geschrieben:
> On 14 February 2015 at 01:43, Programmingkid <programmingkidx@gmail.com> wrote:
> > Added features:
> > Menu items to switch floppy and CD image files.
> > Menu items to eject floppy and CD image files.
> > Menu item to use /dev/cdrom.
> > Verifies with the user before quitting QEMU by displaying a dialog box.
> >
> > Signed-off-by: John Arbuckle <programmingkidx@gmail.com>
>
> Stefan, Kevin -- could you review the bits of this patch
> which determine whether the machine has a floppy/cdrom
> drive and if so let the user insert/inject it, please?
> (that's the emulatorHasDevice and ejectFloppy/changeFloppy
> functions, mostly). I don't know the block layer APIs so
> I can't really say if this patch is doing it in the best/
> non-deprecated/etc way or not...
Well, it's trying to detect the floppy/cdrom device by comparing string
with default IDs that can be overridden by the user, so no, that's
probably far from the best way to do it. The code also doesn't consider
that you could have more than one floppy or cdrom drive.
The correct way is probably to just display any removable block device,
and ideally also to implement some notifiers to deal with hotplug.
Kevin
next prev parent reply other threads:[~2015-02-16 10:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 1:43 [Qemu-devel] [PATCH v3] ui/cocoa.m: Machine menu patch for Mac OS X Programmingkid
2015-02-14 2:28 ` Peter Maydell
2015-02-16 10:08 ` Kevin Wolf [this message]
[not found] ` <4A70459E-56F8-4360-A795-D9ABED95324D@gmail.com>
[not found] ` <20150216154254.GJ4079@noname.str.redhat.com>
2015-02-16 16:12 ` Programmingkid
2015-02-16 16:22 ` Kevin Wolf
2015-02-16 17:00 ` Programmingkid
2015-02-17 9:07 ` Kevin Wolf
2015-02-17 9:41 ` Peter Maydell
2015-02-17 9:57 ` Kevin Wolf
2015-02-17 15:52 ` Programmingkid
2015-02-17 12:41 ` Markus Armbruster
2015-02-16 23:41 ` Peter Maydell
2015-02-17 1:55 ` Programmingkid
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=20150216100821.GA4079@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=programmingkidx@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).