From: Peter Xu <peterx@redhat.com>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: qemu-devel@nongnu.org, qemu-trivial@nongnu.org,
Fabiano Rosas <farosas@suse.de>
Subject: Re: [PATCH] migration: Fix format in error message
Date: Mon, 11 Mar 2024 09:15:19 -0400 [thread overview]
Message-ID: <Ze8D5xYwXfTNHCob@x1n> (raw)
In-Reply-To: <20240311123439.16844-1-anthony.perard@citrix.com>
On Mon, Mar 11, 2024 at 12:34:39PM +0000, Anthony PERARD wrote:
> From: Anthony PERARD <anthony.perard@citrix.com>
>
> In file_write_ramblock_iov(), "offset" is "uintptr_t" and not
> "ram_addr_t". While usually they are both equivalent, this is not the
> case with CONFIG_XEN_BACKEND.
>
> Use the right format. This will fix build on 32-bit.
>
> Fixes: f427d90b9898 ("migration/multifd: Support outgoing mapped-ram stream format")
> Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
Rather than waiting for a trivial pull, I'll queue this for 9.0. Thanks.
--
Peter Xu
prev parent reply other threads:[~2024-03-11 13:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 12:34 [PATCH] migration: Fix format in error message Anthony PERARD
2024-03-11 13:15 ` Peter Xu [this message]
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=Ze8D5xYwXfTNHCob@x1n \
--to=peterx@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=farosas@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).