qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: famz@redhat.com, qemu-devel@nongnu.org, mreitz@redhat.com,
	stefanha@redhat.com, den@openvz.org, John Snow <jsnow@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v7] spec: add qcow2 bitmaps extension specification
Date: Tue, 19 Jan 2016 18:29:23 +0100	[thread overview]
Message-ID: <20160119172923.GG4579@noname.redhat.com> (raw)
In-Reply-To: <569DFA95.5020409@virtuozzo.com>

Am 19.01.2016 um 09:57 hat Vladimir Sementsov-Ogievskiy geschrieben:
> On 19.01.2016 00:16, Eric Blake wrote:
> >preserving semantics of those extra_data bytes).  We
> >have enough room for future extension, and that's good e
> 
> Ok, so, what should go to the spec? Current wording is ok? Just
> delete "Type-specific":
> 
> +
> +        20 - 23:    extra_data_size
> +                    Size of type-specific extra data.
> +
> +                    For now, as no extra data is defined, extra_data_size is
> +                    reserved and must be zero.
> +
> +        variable:   Extra data for the bitmap.

Please be explicit that if extra_data_size is non-zero, the bitmap must
not be used (i.e. specify the incompatible-feature-bit-like behaviour).

Kevin

  reply	other threads:[~2016-01-19 17:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11 13:05 [Qemu-devel] [PATCH v7] spec: add qcow2 bitmaps extension specification Vladimir Sementsov-Ogievskiy
2016-01-12  0:30 ` John Snow
2016-01-14 11:35   ` Denis V. Lunev
2016-01-14 16:42     ` John Snow
2016-01-14 22:08 ` Eric Blake
2016-01-14 23:26   ` John Snow
2016-01-16 14:06     ` Vladimir Sementsov-Ogievskiy
2016-01-18 16:54       ` John Snow
2016-01-18 21:16         ` Eric Blake
2016-01-19  8:57           ` Vladimir Sementsov-Ogievskiy
2016-01-19 17:29             ` Kevin Wolf [this message]
2016-01-25 10:15               ` Vladimir Sementsov-Ogievskiy
2016-01-25 11:09                 ` Kevin Wolf
2016-01-25 12:27                   ` Vladimir Sementsov-Ogievskiy
2016-01-19 17:27           ` Kevin Wolf
2016-01-25 10:22             ` Vladimir Sementsov-Ogievskiy
2016-01-19 17:48 ` Kevin Wolf
2016-01-20 12:34   ` Vladimir Sementsov-Ogievskiy
2016-01-20 21:22     ` John Snow
2016-01-21  8:22       ` Vladimir Sementsov-Ogievskiy
2016-01-21  9:53         ` Kevin Wolf
2016-01-21 10:44           ` Vladimir Sementsov-Ogievskiy

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=20160119172923.GG4579@noname.redhat.com \
    --to=kwolf@redhat.com \
    --cc=den@openvz.org \
    --cc=famz@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vsementsov@virtuozzo.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).