From: Paolo Bonzini <pbonzini@redhat.com>
To: quintela@redhat.com,
"Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
Cc: anthony.perard@citrix.com, qemu-devel@nongnu.org,
stefano.stabellini@eu.citrix.com
Subject: Re: [Qemu-devel] [For 2.5?? PATCH 1/1] qemu_{real_}host_page_[size|mask] change types to ram_addr_t
Date: Wed, 2 Dec 2015 11:54:25 +0100 [thread overview]
Message-ID: <565ECDE1.9030604@redhat.com> (raw)
In-Reply-To: <87fuzlktz2.fsf@emacs.mitica>
On 02/12/2015 11:47, Juan Quintela wrote:
> Reviewed-by: Juan Quintela <quintela@redhat.com>
>
> If nobody complains, I will sent this on next migration pull requset.
>
> Paolo, I think that I preffer this that trusting the intptr_t sign
> extension, but I can be convinced either way. What do you think?
It's not trusting, it's the way C works, but I'm okay either way.
Paolo
next prev parent reply other threads:[~2015-12-02 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 10:43 [Qemu-devel] [For 2.5?? PATCH 1/1] qemu_{real_}host_page_[size|mask] change types to ram_addr_t Dr. David Alan Gilbert (git)
2015-12-02 10:47 ` Juan Quintela
2015-12-02 10:54 ` Paolo Bonzini [this message]
2015-12-02 11:27 ` Dr. David Alan Gilbert
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=565ECDE1.9030604@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefano.stabellini@eu.citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.