From: Eric Blake <eblake@redhat.com>
To: Zhe Qiu <phoeagon@gmail.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v3] block/vdi: Use bdrv_flush after metadata updates
Date: Thu, 07 May 2015 09:05:16 -0600 [thread overview]
Message-ID: <554B7F2C.1040206@redhat.com> (raw)
In-Reply-To: <1430971496-32659-1-git-send-email-phoeagon@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1531 bytes --]
On 05/06/2015 10:04 PM, Zhe Qiu wrote:
> From: phoeagon <phoeagon@gmail.com>
>
> In reference to b0ad5a455d7e5352d4c86ba945112011dbeadfb8~078a458e077d6b0db262c4b05fee51d01de2d1d2, metadata writes to qcow2/cow/qcow/vpc/vmdk are all synced prior to succeeding writes.
>
Please wrap commit comments to be under 80 columns (in fact, under 72 is
good, because 'git log' adds spaces when displaying commit bodies).
Your notation of commit~commit is unusual; ranges in git are usually
spelled commit..commit. Also, it's okay to abbreviate commit SHAs to 8
bytes or so. So to shrink your long line, I'd write b0ad5a45..078a458e.
> Only when write is successful that bdrv_flush is called.
>
> Signed-off-by: Zhe Qiu <phoeagon@gmail.com>
Your 'From:' and 'Signed-off-by:' lines have different spellings, which
makes it more confusing when searching for patches by you. You can add
an entry to .mailmap (as a separate patch) to retro-actively consolidate
entries, but it is better to catch things like this up front before we
even have the problem of separate names.
I suspect you want "Zhe Qiu" as the spelling of your name in both lines
(git config can be taught to set up the preferred name to attribute both
for signing patches and for sending email). It is also acceptable to
use UTF-8 to spell your name in native characters, or even a combination
of "native name (ascii counterpart)"
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-05-07 15:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 4:04 [Qemu-devel] [PATCH v3] block/vdi: Use bdrv_flush after metadata updates Zhe Qiu
2015-05-07 10:09 ` Stefan Hajnoczi
2015-05-07 15:05 ` Eric Blake [this message]
2015-05-07 15:16 ` [Qemu-devel] [PATCH v4] " Zhe Qiu
2015-05-08 13:14 ` Max Reitz
2015-05-08 13:55 ` Kevin Wolf
2015-05-08 14:43 ` phoeagon
2015-05-08 21:26 ` Stefan Weil
2015-05-09 3:54 ` phoeagon
2015-05-09 3:59 ` phoeagon
2015-05-09 6:39 ` Stefan Weil
2015-05-09 7:41 ` phoeagon
2015-05-10 15:01 ` Paolo Bonzini
2015-05-10 16:02 ` Stefan Weil
2015-05-10 16:05 ` phoeagon
2015-05-10 16:10 ` Paolo Bonzini
2015-05-10 16:26 ` Stefan Weil
2015-05-10 17:14 ` phoeagon
2015-05-08 10:43 ` [Qemu-devel] [Qemu-block] [PATCH v3] " Kevin Wolf
2015-05-08 11:50 ` phoeagon
2015-05-08 12:02 ` Kevin Wolf
2015-05-08 12:56 ` phoeagon
2015-05-08 13:10 ` [Qemu-devel] " Max Reitz
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=554B7F2C.1040206@redhat.com \
--to=eblake@redhat.com \
--cc=mreitz@redhat.com \
--cc=phoeagon@gmail.com \
--cc=qemu-block@nongnu.org \
--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).