All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Benoît Canet" <benoit.canet@nodalink.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] raw-posix: Fix raw_co_get_block_status()
Date: Wed, 08 Oct 2014 21:43:19 +0200	[thread overview]
Message-ID: <543593D7.4070909@redhat.com> (raw)
In-Reply-To: <1411400179-10605-1-git-send-email-mreitz@redhat.com>

On 22.09.2014 17:36, Max Reitz wrote:
> raw_co_get_block_status() should return 0 and set *pnum to 0 after the
> EOF; currently it does this merely by accident, so implement it
> directly. Also, nb_sectors should be clamped against the image end.
>
> While doing that, centralize the generation of
> raw_co_get_block_status()'s return value along the way.
>
>
> v2:
> - Patch 1: Clamp nb_sectors against image end
> - Patch 2: Fix alignment issue
>
>
> Max Reitz (2):
>    raw-posix: Fix raw_co_get_block_status() after EOF
>    raw-posix: raw_co_get_block_status() return value
>
>   block/raw-posix.c | 36 ++++++++++++++++++++++--------------
>   1 file changed, 22 insertions(+), 14 deletions(-)

Ping. (This should be rather simple to review)

  parent reply	other threads:[~2014-10-08 19:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 15:36 [Qemu-devel] [PATCH v2 0/2] raw-posix: Fix raw_co_get_block_status() Max Reitz
2014-09-22 15:36 ` [Qemu-devel] [PATCH v2 1/2] raw-posix: Fix raw_co_get_block_status() after EOF Max Reitz
2014-10-09  4:13   ` Eric Blake
2014-10-16  8:30   ` Kevin Wolf
2014-09-22 15:36 ` [Qemu-devel] [PATCH v2 2/2] raw-posix: raw_co_get_block_status() return value Max Reitz
2014-10-09  4:16   ` Eric Blake
2014-10-08 19:43 ` Max Reitz [this message]
2014-10-09 18:58   ` [Qemu-devel] [PATCH v2 0/2] raw-posix: Fix raw_co_get_block_status() Benoît Canet
2014-10-11  8:55     ` 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=543593D7.4070909@redhat.com \
    --to=mreitz@redhat.com \
    --cc=benoit.canet@nodalink.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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.