qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Jeff Cody <jcody@redhat.com>
Cc: kwolf@redhat.com, pbonzini@redhat.com, qemu-devel@nongnu.org,
	armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/2] VHDX endian fixes, error reporting
Date: Thu, 7 Aug 2014 11:05:15 +0100	[thread overview]
Message-ID: <20140807100515.GC32038@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <cover.1407353952.git.jcody@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 776 bytes --]

On Wed, Aug 06, 2014 at 03:54:56PM -0400, Jeff Cody wrote:
> This series is mainly for some bug fixes related to VHDX endianness, stemming
> from code reviews done by Markus Armbruster and Paolo Bonzini.  Once I did some
> testing on a big-endian machine, several more endian related errors were
> discovered, as well.  All endian related fixes are in patch 2.
> 
> Jeff Cody (2):
>   block: vhdx - add error check
>   block: VHDX endian fixes
> 
>  block/vhdx-endian.c | 11 +++++--
>  block/vhdx-log.c    | 48 ++++++++++++++++++-----------
>  block/vhdx.c        | 89 +++++++++++++++++++++++++++++++----------------------
>  block/vhdx.h        |  1 +
>  4 files changed, 93 insertions(+), 56 deletions(-)

Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>

[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]

  parent reply	other threads:[~2014-08-07 10:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-06 19:54 [Qemu-devel] [PATCH 0/2] VHDX endian fixes, error reporting Jeff Cody
2014-08-06 19:54 ` [Qemu-devel] [PATCH 1/2] block: vhdx - add error check Jeff Cody
2014-08-06 19:54 ` [Qemu-devel] [PATCH 2/2] block: VHDX endian fixes Jeff Cody
2014-08-07 10:05 ` Stefan Hajnoczi [this message]
2014-08-07 14:07   ` [Qemu-devel] [PATCH 0/2] VHDX endian fixes, error reporting 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=20140807100515.GC32038@stefanha-thinkpad.redhat.com \
    --to=stefanha@redhat.com \
    --cc=armbru@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --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).