All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH 1/4 v3] block: add image fragmentation statistics to qemu-img
Date: Mon, 02 Apr 2012 18:13:47 +0200	[thread overview]
Message-ID: <4F79D03B.2050706@redhat.com> (raw)
In-Reply-To: <1331813614-3754-1-git-send-email-wdongxu@linux.vnet.ibm.com>

Am 15.03.2012 13:13, schrieb Dong Xu Wang:
> From: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>
> 
> Discussion can be found at:
> http://patchwork.ozlabs.org/patch/128730/
> 
> This patch add image fragmentation statistics while using qemu-img check.
> 
> Signed-off-by: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>

Thanks, applied all to the block branch.

Please make the subject line prefix more specific in future commits, I
changed it for this series. For example, don't write "block: foo in qed"
or "block: Add bar to qemu-img", but "qed: foo" and "qemu-img: Add bar".
The "block:" prefix is reserved for changes that are purely in the
generic block layer (mainly block.c, blockdev.c).

Kevin

  parent reply	other threads:[~2012-04-02 16:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15 12:13 [Qemu-devel] [PATCH 1/4 v3] block: add image fragmentation statistics to qemu-img Dong Xu Wang
2012-03-15 12:13 ` [Qemu-devel] [PATCH 2/4 v3] block: image fragmentation statistics for qed Dong Xu Wang
2012-03-15 12:13 ` [Qemu-devel] [PATCH 3/4 v3] block: add dirty flag status to qemu-img Dong Xu Wang
2012-03-15 12:13 ` [Qemu-devel] [PATCH 4/4] block: track dirty flag status in qed Dong Xu Wang
2012-03-15 12:45 ` [Qemu-devel] [PATCH 1/4 v3] block: add image fragmentation statistics to qemu-img Stefan Hajnoczi
2012-03-29 15:56   ` Stefan Hajnoczi
2012-03-29 16:00 ` Stefan Hajnoczi
2012-04-02 16:13 ` Kevin Wolf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-03-15 12:47 Dong Xu Wang

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=4F79D03B.2050706@redhat.com \
    --to=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.com \
    --cc=wdongxu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.