qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] qcow2: Alignment of snapshot table entries
Date: Wed, 9 Oct 2013 11:41:56 +0200	[thread overview]
Message-ID: <20131009094156.GE8994@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <1381307650-13799-1-git-send-email-mreitz@redhat.com>

Am 09.10.2013 um 10:34 hat Max Reitz geschrieben:
> The qcow2 specification does not explicitly state so far that every
> snapshot table entry is aligned to 8 bytes. QEMU, in contrast, does this
> alignment, thus it should be properly documented (which this patch
> does).
> 
> Signed-off-by: Max Reitz <mreitz@redhat.com>

Thanks, applied to the block branch.

Kevin

      reply	other threads:[~2013-10-09  9:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09  8:34 [Qemu-devel] [PATCH] qcow2: Alignment of snapshot table entries Max Reitz
2013-10-09  9:41 ` Kevin Wolf [this message]

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=20131009094156.GE8994@dhcp-200-207.str.redhat.com \
    --to=kwolf@redhat.com \
    --cc=mreitz@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 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).