qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v2 0/2] block: Add qemu_dup in osdep.c and use it
Date: Thu, 7 Jul 2016 17:14:13 -0400	[thread overview]
Message-ID: <bd2841cb-ea6b-a0b0-0eb8-acf829282f6c@redhat.com> (raw)
In-Reply-To: <20160622125320.31279-1-famz@redhat.com>



On 06/22/2016 08:53 AM, Fam Zheng wrote:
> v2: Fix patch 1 #else branch, and "r" => "ret". [Kevin]
>     Add Kevin's r-b line in patch 2.
> 
> This is an independent tiny change extracted from the image locking series,
> which can be processed separately.
> 
> Improved according to Kevin's suggestion in v6 image locking series.
> 
> Fam
> 
> 
> Fam Zheng (2):
>   osdep: Introduce qemu_dup
>   raw-posix: Use qemu_dup
> 
>  block/raw-posix.c    | 10 +---------
>  include/qemu/osdep.h |  3 +++
>  util/osdep.c         | 23 +++++++++++++++--------
>  3 files changed, 19 insertions(+), 17 deletions(-)
> 

You submitted two versions of this, I think this is the right one.

Reviewed-by: John Snow <jsnow@redhat.com>

  parent reply	other threads:[~2016-07-07 21:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-22 12:53 [Qemu-devel] [PATCH v2 0/2] block: Add qemu_dup in osdep.c and use it Fam Zheng
2016-06-22 12:53 ` [Qemu-devel] [PATCH v2 1/2] osdep: Introduce qemu_dup Fam Zheng
2016-06-22 15:21   ` Eric Blake
2016-06-22 15:24     ` Eric Blake
2016-06-22 12:53 ` [Qemu-devel] [PATCH v2 2/2] raw-posix: Use qemu_dup Fam Zheng
2016-07-07 21:14 ` John Snow [this message]
2016-07-08 10:17   ` [Qemu-devel] [Qemu-block] [PATCH v2 0/2] block: Add qemu_dup in osdep.c and use it Kevin Wolf

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=bd2841cb-ea6b-a0b0-0eb8-acf829282f6c@redhat.com \
    --to=jsnow@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.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).