From: "Andreas Färber" <afaerber@suse.de>
To: Keith Busch <keith.busch@intel.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH qom-next v3 12/15] nvme: Permit zero-length block devices
Date: Thu, 27 Mar 2014 17:35:51 +0100 [thread overview]
Message-ID: <53345367.2040402@suse.de> (raw)
In-Reply-To: <alpine.LRH.2.03.1403121346570.2885@AMR>
Hi Keith,
Am 12.03.2014 21:13, schrieb Keith Busch:
> On Wed, 12 Mar 2014, Andreas Färber wrote:
>> Tonight is Hard Freeze for 2.0. If you could also review the matching
>> test case http://patchwork.ozlabs.org/patch/329627/ I would put both in
>> my pull.
>
> Looks great! I'd apply the new test case, but it won't without the
> previous "pvpanic-test" patch in your series.
I had held off putting them in my pull for -rc0, but not seeing
patches/pull from your side I am queuing them now for -rc1. Can I
formalize your review as an Acked-by of both, if not turn your
Signed-off-by into a Reviewed-by for this patch here?
Thanks,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-03-27 16:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 18:28 [Qemu-devel] [PATCH qom-next v3 00/15] qtest: Prepare virtio, other PCI tests Andreas Färber
2014-03-12 18:28 ` [Qemu-devel] [PATCH qom-next v3 01/15] tests: Clean up IndustryPack TCPI200 gcov paths Andreas Färber
2014-03-12 18:28 ` [Qemu-devel] [PATCH qom-next v3 02/15] tests: Add virtio-blk qtest Andreas Färber
2014-03-12 18:28 ` [Qemu-devel] [PATCH qom-next v3 03/15] tests: Add virtio-balloon qtest Andreas Färber
2014-03-12 18:28 ` [Qemu-devel] [PATCH qom-next v3 04/15] tests: Add virtio-rng qtest Andreas Färber
2014-03-12 18:28 ` [Qemu-devel] [PATCH qom-next v3 05/15] tests: Add virtio-scsi qtest Andreas Färber
2014-03-12 18:31 ` Paolo Bonzini
2014-03-12 18:28 ` [Qemu-devel] [PATCH qom-next v3 06/15] tests: Add virtio-9p qtest Andreas Färber
2014-03-27 16:01 ` Andreas Färber
2014-03-27 16:29 ` Paolo Bonzini
2014-03-12 18:28 ` [Qemu-devel] [PATCH qom-next v3 07/15] tests: Add virtio-serial qtest Andreas Färber
2014-03-12 18:28 ` [Qemu-devel] [PATCH qom-next v3 08/15] tests: Add virtio-console qtest Andreas Färber
2014-03-12 18:28 ` [Qemu-devel] [PATCH qom-next v3 09/15] tests: Add pvpanic qtest Andreas Färber
2014-03-12 18:28 ` [Qemu-devel] [PATCH qom-next v3 10/15] qtest: Factor out qtest_qmp_receive() Andreas Färber
2014-03-12 18:28 ` [Qemu-devel] [PATCH qom-next v3 11/15] pvpanic-test: Assert pause event Andreas Färber
2014-03-12 18:28 ` [Qemu-devel] [PATCH qom-next v3 12/15] nvme: Permit zero-length block devices Andreas Färber
2014-03-12 19:13 ` Keith Busch
2014-03-12 19:20 ` Andreas Färber
2014-03-12 20:13 ` Keith Busch
2014-03-27 16:35 ` Andreas Färber [this message]
2014-03-27 19:00 ` Keith Busch
2014-03-12 18:28 ` [Qemu-devel] [PATCH qom-next v3 13/15] tests: Add nvme qtest Andreas Färber
2014-03-27 16:40 ` Andreas Färber
2014-03-12 18:28 ` [Qemu-devel] [PATCH qom-next v3 14/15] tests: Add i82801b11 qtest Andreas Färber
2014-03-27 17:02 ` Andreas Färber
2014-03-12 18:28 ` [Qemu-devel] [PATCH qom-next v3 15/15] tests: Add spapr-pci-host-bridge qtest Andreas Färber
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=53345367.2040402@suse.de \
--to=afaerber@suse.de \
--cc=keith.busch@intel.com \
--cc=kwolf@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).