From: Eric Blake <eblake@redhat.com>
To: Maria Kustova <maxa@catit.be>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, Maria Kustova <maria.k@catit.be>, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] docs: Define refcount_bits value
Date: Fri, 23 May 2014 07:45:56 -0600 [thread overview]
Message-ID: <537F5114.9060402@redhat.com> (raw)
In-Reply-To: <1400852489-31099-1-git-send-email-maria.k@catit.be>
[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]
On 05/23/2014 07:41 AM, Maria Kustova wrote:
> The 'refcount_bits' term used in the description of refcount block entry is
> not defined in the specification. The definition is added in the
> 'refcount_order' section where refcount_bits was used as 'width in bits'.
>
> Signed-off-by: Maria Kustova <maria.k@catit.be>
> ---
> docs/specs/qcow2.txt | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
Reviewed-by: Eric Blake <eblake@redhat.com>
>
> diff --git a/docs/specs/qcow2.txt b/docs/specs/qcow2.txt
> index f19536a..3f713a6 100644
> --- a/docs/specs/qcow2.txt
> +++ b/docs/specs/qcow2.txt
> @@ -107,8 +107,9 @@ in the description of a field.
>
> 96 - 99: refcount_order
> Describes the width of a reference count block entry (width
> - in bits = 1 << refcount_order). For version 2 images, the
> - order is always assumed to be 4 (i.e. the width is 16 bits).
> + in bits: refcount_bits = 1 << refcount_order). For version 2
> + images, the order is always assumed to be 4
> + (i.e. refcount_bits = 16).
>
> 100 - 103: header_length
> Length of the header structure in bytes. For version 2
>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2014-05-23 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 13:41 [Qemu-devel] [PATCH] docs: Define refcount_bits value Maria Kustova
2014-05-23 13:45 ` Eric Blake [this message]
2014-05-23 13:56 ` Eric Blake
2014-05-23 15:20 ` Stefan Hajnoczi
2014-05-23 15:21 ` Stefan Hajnoczi
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=537F5114.9060402@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=maria.k@catit.be \
--cc=maxa@catit.be \
--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).