From: Kevin Wolf <kwolf@redhat.com>
To: Tal Kain <tal.kain@ravellosystems.com>
Cc: hvx@ravellosystems.com, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] raw-win32.c: Fix incorrect handling behaviour of small block files
Date: Mon, 9 Sep 2013 11:31:57 +0200 [thread overview]
Message-ID: <20130909093157.GD3110@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <1378718095-18850-1-git-send-email-tal.kain@ravellosystems.com>
Am 09.09.2013 um 11:14 hat Tal Kain geschrieben:
> It is a valid case that the read data's size is smaller than the
> requested size since there could be files that are smaller than
> the minimum block size (For ex. when a VMDK disk descriptor file)
>
> Signed-off-by: Tal Kain <tal.kain@ravellosystems.com>
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2013-09-09 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 9:14 [Qemu-devel] [PATCH] raw-win32.c: Fix incorrect handling behaviour of small block files Tal Kain
2013-09-09 9:31 ` 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=20130909093157.GD3110@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=hvx@ravellosystems.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=tal.kain@ravellosystems.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).