From: Kevin Wolf <kwolf@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org, armbru@redhat.com,
mreitz@redhat.com, fred.konrad@greensocs.com
Subject: Re: [Qemu-devel] [PATCH v5 0/4] fdc: Use separate qdev device for drives
Date: Tue, 25 Oct 2016 11:02:24 +0200 [thread overview]
Message-ID: <20161025090224.GC4695@noname.str.redhat.com> (raw)
In-Reply-To: <4d44da4e-ef4a-d8bc-154c-fc91e96a96df@redhat.com>
Am 24.10.2016 um 20:44 hat John Snow geschrieben:
> On 10/24/2016 07:37 AM, Kevin Wolf wrote:
> >We have been complaining for a long time about how the floppy controller and
> >floppy drives are combined in a single qdev device and how this makes the
> >device awkward to work with because it behaves different from all other block
> >devices.
>
> [...]
>
> >Alberto Garcia (2):
> > throttle: Correct access to wrong BlockBackendPublic structures
> > qemu-iotests: Test I/O in a single drive from a throttling group
> >
> >Halil Pasic (1):
> > block: improve error handling in raw_open
> >
> >Pino Toscano (1):
> > qapi: fix memory leak in bdrv_image_info_specific_dump
> >
>
> uhhh
>
> http://i.imgur.com/60YQvmg.png
wtf did I do there? :-/
I'll send a new version... But if it continues like this, we'll miss the
freeze...
Kevin
prev parent reply other threads:[~2016-10-25 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 11:37 [Qemu-devel] [PATCH v5 0/4] fdc: Use separate qdev device for drives Kevin Wolf
2016-10-24 11:37 ` [Qemu-devel] [PATCH v5 1/4] block: improve error handling in raw_open Kevin Wolf
2016-10-24 11:37 ` [Qemu-devel] [PATCH v5 2/4] qapi: fix memory leak in bdrv_image_info_specific_dump Kevin Wolf
2016-10-24 11:37 ` [Qemu-devel] [PATCH v5 3/4] throttle: Correct access to wrong BlockBackendPublic structures Kevin Wolf
2016-10-24 11:37 ` [Qemu-devel] [PATCH v5 4/4] qemu-iotests: Test I/O in a single drive from a throttling group Kevin Wolf
2016-10-24 18:44 ` [Qemu-devel] [PATCH v5 0/4] fdc: Use separate qdev device for drives John Snow
2016-10-25 9:02 ` 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=20161025090224.GC4695@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=fred.konrad@greensocs.com \
--cc=jsnow@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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).