qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel@nongnu.org
Cc: "Keith Busch" <keith.busch@intel.com>,
	"Kevin Wolf" <kwolf@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>,
	"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: [Qemu-devel] [PULL for-2.0 06/16] nvme: Permit zero-length block devices
Date: Mon, 31 Mar 2014 23:10:52 +0200	[thread overview]
Message-ID: <1396300262-10430-7-git-send-email-afaerber@suse.de> (raw)
In-Reply-To: <1396300262-10430-1-git-send-email-afaerber@suse.de>

It may not be sensible for normal use cases, but it allows to use
/dev/null in QTest.

Acked-by: Keith Busch <keith.busch@intel.com>
Signed-off-by: Andreas Färber <afaerber@suse.de>
---
 hw/block/nvme.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/hw/block/nvme.c b/hw/block/nvme.c
index 2882ffe..5fd8f89 100644
--- a/hw/block/nvme.c
+++ b/hw/block/nvme.c
@@ -752,8 +752,8 @@ static int nvme_init(PCIDevice *pci_dev)
         return -1;
     }
 
-    bs_size =  bdrv_getlength(n->conf.bs);
-    if (bs_size <= 0) {
+    bs_size = bdrv_getlength(n->conf.bs);
+    if (bs_size < 0) {
         return -1;
     }
 
-- 
1.8.4.5

  parent reply	other threads:[~2014-03-31 21:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31 21:10 [Qemu-devel] [PULL for-2.0 00/16] QOM devices patch queue 2014-03-31 Andreas Färber
2014-03-31 21:10 ` [Qemu-devel] [PULL for-2.0 01/16] Revert "qtest: Fix crash if SIGABRT during qtest_init()" Andreas Färber
2014-03-31 21:10 ` [Qemu-devel] [PULL for-2.0 02/16] qtest: Keep list of qtest instances for SIGABRT handler Andreas Färber
2014-03-31 21:10 ` [Qemu-devel] [PULL for-2.0 03/16] tests: Remove unsupported tests for MinGW Andreas Färber
2014-03-31 21:10 ` [Qemu-devel] [PULL for-2.0 04/16] tests: Skip POSIX-only tests on Windows Andreas Färber
2014-03-31 21:10 ` [Qemu-devel] [PULL for-2.0 05/16] tests: Correctly skip qtest on non-POSIX hosts Andreas Färber
2014-03-31 21:10 ` Andreas Färber [this message]
2014-03-31 21:10 ` [Qemu-devel] [PULL for-2.0 07/16] tests: Add nvme qtest Andreas Färber
2014-03-31 21:10 ` [Qemu-devel] [PULL for-2.0 08/16] tests: Add virtio-9p qtest Andreas Färber
2014-03-31 21:10 ` [Qemu-devel] [PULL for-2.0 09/16] tests: Add pvpanic qtest Andreas Färber
2014-03-31 21:10 ` [Qemu-devel] [PULL for-2.0 10/16] qtest: Factor out qtest_qmp_receive() Andreas Färber
2014-03-31 21:10 ` [Qemu-devel] [PULL for-2.0 11/16] pvpanic-test: Assert pause event Andreas Färber
2014-03-31 21:10 ` [Qemu-devel] [PULL for-2.0 12/16] tests: Add i82801b11 qtest Andreas Färber
2014-03-31 21:10 ` [Qemu-devel] [PULL for-2.0 13/16] tmp105: Read temperature in milli-celsius Andreas Färber
2014-03-31 21:11 ` [Qemu-devel] [PULL for-2.0 14/16] tmp105-test: Wrap simple building blocks for testing Andreas Färber
2014-03-31 21:11 ` [Qemu-devel] [PULL for-2.0 15/16] tmp105-test: Add a second sensor and test that one Andreas Färber
2014-03-31 21:11 ` [Qemu-devel] [PULL for-2.0 16/16] tmp105-test: Test QOM property and precision Andreas Färber
2014-04-01 16:09 ` [Qemu-devel] [PULL for-2.0 00/16] QOM devices patch queue 2014-03-31 Peter Maydell

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=1396300262-10430-7-git-send-email-afaerber@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).