From: Stefan Hajnoczi <stefanha@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: kwolf@redhat.com, Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] block/vmdk: do not report file offset for compressed extents
Date: Fri, 28 Feb 2014 11:30:22 +0100 [thread overview]
Message-ID: <20140228103022.GD30385@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <530F103A.7090705@kamp.de>
On Thu, Feb 27, 2014 at 11:15:22AM +0100, Peter Lieven wrote:
> Signed-off-by: Peter Lieven <pl@kamp.de>
> ---
> block/vmdk.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
next prev parent reply other threads:[~2014-02-28 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 10:15 [Qemu-devel] [PATCH] block/vmdk: do not report file offset for compressed extents Peter Lieven
2014-02-28 10:30 ` Stefan Hajnoczi [this message]
[not found] <1393408077-556-1-git-send-email-pl@kamp.de>
2014-02-26 10:17 ` Fam Zheng
2014-02-27 10:06 ` Stefan Hajnoczi
2014-02-27 10:15 ` Peter Lieven
2014-02-27 15:49 ` Stefan Hajnoczi
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=20140228103022.GD30385@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pl@kamp.de \
--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).