From: Kevin Wolf <kwolf@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-block@nongnu.org, famz@redhat.com, qemu-devel@nongnu.org,
armbru@redhat.com, mreitz@redhat.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [RFC PATCH 0/7] BlockBackends, nodes and guest devices
Date: Tue, 12 Jul 2016 10:14:42 +0200 [thread overview]
Message-ID: <20160712081442.GA4478@noname.redhat.com> (raw)
In-Reply-To: <130cebe0-b23e-1e62-3b0f-e9561c5d9f41@redhat.com>
Am 12.07.2016 um 02:13 hat John Snow geschrieben:
> No oxford comma in the subject? :)
It's already hard enough to keep the German comma rules straight and
avoid confusing the pre-reform rules with the post-reform ones. I don't
think I should bother with the comma rules of a language where even the
native speakers can't seem to agree. :-)
(But thanks, I wasn't aware that this disagreement even exists before
reading it up now.)
> On 06/23/2016 10:36 AM, Kevin Wolf wrote:
> 1-4: Reviewed-by: John Snow <jsnow@redhat.com>
> 5: Looks good, pending discussion on the right thing to name "ID", but
> the patch itself looks perfectly cromulent.
> 6: Causes only a minor regression in 030 due to different error class
> names, but R-B otherwise.
> 7: No opinion. Looks sane mechanically but I don't know enough about
> core block properties to have a meaningful opinion. "ACK."
Thanks!
> For non-RFC, some new iotests would be good.
Anything specific you have in mind to be tested?
The problem with everything related to devices is that it requires
running a qemu process and most likely a specific machine type. But I
guess we can just skip some tests if we don't have the right binary.
Kevin
next prev parent reply other threads:[~2016-07-12 8:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 14:36 [Qemu-devel] [RFC PATCH 0/7] BlockBackends, nodes and guest devices Kevin Wolf
2016-06-23 14:36 ` [Qemu-devel] [RFC PATCH 1/7] block/qdev: Allow node name for drive properties Kevin Wolf
2016-06-24 17:35 ` Eric Blake
2016-06-24 17:54 ` Kevin Wolf
2016-06-23 14:36 ` [Qemu-devel] [RFC PATCH 2/7] block: Add blk_by_dev() Kevin Wolf
2016-06-24 17:39 ` Eric Blake
2016-06-23 14:36 ` [Qemu-devel] [RFC PATCH 3/7] qdev-monitor: Factor out find_device_state() Kevin Wolf
2016-06-24 17:41 ` Eric Blake
2016-06-23 14:36 ` [Qemu-devel] [RFC PATCH 4/7] qdev-monitor: Add blk_by_qdev_id() Kevin Wolf
2016-06-24 20:22 ` Eric Blake
2016-06-23 14:36 ` [Qemu-devel] [RFC PATCH 5/7] block: Accept device model name for blockdev-open/close-tray Kevin Wolf
2016-06-24 20:39 ` Eric Blake
2016-06-27 8:53 ` Kevin Wolf
2016-06-23 14:36 ` [Qemu-devel] [RFC PATCH 6/7] block: Accept node-name for block-stream Kevin Wolf
2016-06-24 20:57 ` Eric Blake
2016-06-23 14:36 ` [Qemu-devel] [RFC PATCH 7/7] block/qdev: Allow configuring WCE with qdev properties Kevin Wolf
2016-06-24 21:10 ` Eric Blake
2016-06-23 21:26 ` [Qemu-devel] [RFC PATCH 0/7] BlockBackends, nodes and guest devices Paolo Bonzini
2016-06-27 16:13 ` Max Reitz
2016-06-27 16:38 ` Kevin Wolf
2016-06-27 16:40 ` Max Reitz
2016-07-12 0:13 ` [Qemu-devel] [Qemu-block] " John Snow
2016-07-12 8:14 ` Kevin Wolf [this message]
2016-07-12 17:11 ` John Snow
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=20160712081442.GA4478@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=jsnow@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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).