From: Yuval Shaia <yuval.shaia@oracle.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-trivial@nongnu.org,
Marcel Apfelbaum <marcel@redhat.com>,
yuval.shaia@oracle.com
Subject: Re: [Qemu-trivial] [PATCH for-2.12] rdma: Fix 32-bit compilation
Date: Tue, 20 Mar 2018 12:43:49 +0200 [thread overview]
Message-ID: <20180320104348.GA3268@yuvallap> (raw)
In-Reply-To: <20180319215335.1119213-1-eblake@redhat.com>
On Mon, Mar 19, 2018 at 04:53:35PM -0500, Eric Blake wrote:
> Use the correct printf formats, so that a 32-bit compile doesn't
> spit out lots of warnings about %lx being incompatible with uint64_t.
> Broken since initial commit ef6d4ccd.
>
> Signed-off-by: Eric Blake <eblake@redhat.com>
> ---
>
> I don't know if 'make vm-build-ubuntu.i368' would catch this (it failed
> for me for other reasons); I found it via a 32-bit rawhide VM.
>
> hw/rdma/rdma_backend.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/hw/rdma/rdma_backend.c b/hw/rdma/rdma_backend.c
> index e306fba5344..89020fdcf62 100644
> --- a/hw/rdma/rdma_backend.c
> +++ b/hw/rdma/rdma_backend.c
> @@ -656,7 +656,8 @@ void rdma_backend_destroy_qp(RdmaBackendQP *qp)
> #define CHK_ATTR(req, dev, member, fmt) ({ \
> pr_dbg("%s="fmt","fmt"\n", #member, dev.member, req->member); \
> if (req->member > dev.member) { \
> - warn_report("%s = 0x%lx is higher than host device capability 0x%lx", \
> + warn_report("%s = 0x%" PRIx64 " is higher than host device " \
> + "capability 0x%" PRIx64, \
> #member, (uint64_t)req->member, (uint64_t)dev.member); \
Hmmm, interesting.
I wonder why in first place to cast all members to uint64_t.
Can you try the method that is used above in the call to pr_dbg, i.e. to
use the given argument fmt?
Something like this:
warn_report("%s = "fmt" is higher than host device capability "fmt, \
#member, req->member, dev.member); \
> req->member = dev.member; \
> } \
> --
> 2.14.3
>
next prev parent reply other threads:[~2018-03-20 13:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 21:53 [Qemu-trivial] [PATCH for-2.12] rdma: Fix 32-bit compilation Eric Blake
2018-03-19 22:08 ` [Qemu-trivial] [Qemu-devel] " Eric Blake
2018-03-20 10:36 ` Marcel Apfelbaum
2018-03-20 10:30 ` [Qemu-trivial] " Marcel Apfelbaum
2018-03-21 1:46 ` Fam Zheng
2018-03-21 2:07 ` Fam Zheng
2018-03-21 9:20 ` Marcel Apfelbaum
2018-03-21 9:34 ` Fam Zheng
2018-03-20 10:43 ` Yuval Shaia [this message]
2018-03-21 16:52 ` Marcel Apfelbaum
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=20180320104348.GA3268@yuvallap \
--to=yuval.shaia@oracle.com \
--cc=eblake@redhat.com \
--cc=marcel@redhat.com \
--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 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.