From: Kevin Wolf <kwolf@redhat.com>
To: Li Zhi Hui <zhihuili@linux.vnet.ibm.com>
Cc: armbru@redhat.com, qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v3] block: Use bdrv functions to replace file operation in cow.c
Date: Tue, 08 Nov 2011 10:59:07 +0100 [thread overview]
Message-ID: <4EB8FD6B.9000405@redhat.com> (raw)
In-Reply-To: <1320733273-17912-1-git-send-email-zhihuili@linux.vnet.ibm.com>
Am 08.11.2011 07:21, schrieb Li Zhi Hui:
> Since common file operation functions lack of error detection,
> so change them to bdrv series functions.
>
> v3: correct some errors
> v2: Only contains the function modified.
> v1: Fix coding style and convert file operation functions to bdrv functions.
>
> Signed-off-by: Li Zhi Hui <zhihuili@linux.vnet.ibm.com>
Thanks, applied to the block branch (for 1.1)
Kevin
prev parent reply other threads:[~2011-11-08 9:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 6:21 [Qemu-devel] [PATCH v3] block: Use bdrv functions to replace file operation in cow.c Li Zhi Hui
2011-11-08 8:23 ` Stefan Hajnoczi
2011-11-08 9:59 ` 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=4EB8FD6B.9000405@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
--cc=zhihuili@linux.vnet.ibm.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).