From: Fam Zheng <famz@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] ramblock: add hmp command "info ramblock"
Date: Thu, 27 Apr 2017 09:12:43 +0800 [thread overview]
Message-ID: <20170427011243.GD9205@lemon.lan> (raw)
In-Reply-To: <1493205192-26743-1-git-send-email-peterx@redhat.com>
On Wed, 04/26 19:13, Peter Xu wrote:
> v2:
> - replace "lx" with "PRIx64" in three places
ram_addr_t doesn't have a fixed bit width, to keep compilers happy, maybe you
can stick to PRIx64 in the format string, and cast the parameters.
Fam
next prev parent reply other threads:[~2017-04-27 1:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 11:13 [Qemu-devel] [PATCH v2 0/2] ramblock: add hmp command "info ramblock" Peter Xu
2017-04-26 11:13 ` [Qemu-devel] [PATCH v2 1/2] ramblock: add RAMBLOCK_FOREACH() Peter Xu
2017-04-26 11:13 ` [Qemu-devel] [PATCH v2 2/2] ramblock: add new hmp command "info ramblock" Peter Xu
2017-04-26 12:23 ` [Qemu-devel] [PATCH v2 0/2] ramblock: add " no-reply
2017-04-27 1:12 ` Fam Zheng [this message]
2017-04-27 2:04 ` Peter Xu
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=20170427011243.GD9205@lemon.lan \
--to=famz@redhat.com \
--cc=dgilbert@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@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).