From: Stefan Hajnoczi <stefanha@gmail.com>
To: Hu Tao <hutao@cn.fujitsu.com>
Cc: Stefan Weil <sw@weilnetz.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] docs/specs/qcow2.txt: fix incorrect bits of offsets in entries
Date: Fri, 17 Jan 2014 15:40:15 +0800 [thread overview]
Message-ID: <20140117074015.GA31039@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1388390417-14381-1-git-send-email-hutao@cn.fujitsu.com>
On Mon, Dec 30, 2013 at 04:00:17PM +0800, Hu Tao wrote:
> Fix incorrect bits of offsets in refcount table entry, l1 table
> entry and l2 table entry. See REFT_OFFSET_MASK, L1E_OFFSET_MASK
> and L2E_OFFSET_MASK.
>
> Fix a typo while at the file.
>
> Signed-off-by: Hu Tao <hutao@cn.fujitsu.com>
> ---
>
> v2: update comments as well.
>
> docs/specs/qcow2.txt | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
next prev parent reply other threads:[~2014-01-17 7:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 8:00 [Qemu-devel] [PATCH v2] docs/specs/qcow2.txt: fix incorrect bits of offsets in entries Hu Tao
2014-01-17 7:40 ` Stefan Hajnoczi [this message]
2014-01-20 9:10 ` Kevin Wolf
2014-01-21 2:56 ` Hu Tao
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=20140117074015.GA31039@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=hutao@cn.fujitsu.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).