From: Alex Netes <alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] opensm/libvendor: Fix compile warnings on 64 bit machines when building --with-osmv=sim
Date: Fri, 3 Jun 2011 13:48:53 +0300 [thread overview]
Message-ID: <20110603104852.GF1098@calypso.voltaire.com> (raw)
In-Reply-To: <4DE7DE6A.9040100-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
On 15:03 Thu 02 Jun , Hal Rosenstock wrote:
>
> osm_vendor_mlx.c: In function '__osmv_get_send_txn':
> osm_vendor_mlx.c:708: warning: format '%llX' expects type 'long long unsigned int', but argument 4 has type 'uint64_t'
> osm_vendor_mlx.c:723: warning: format '%llX' expects type 'long long unsigned int', but argument 4 has type 'uint64_t'
> osm_vendor_mlx.c:733: warning: format '%llX' expects type 'long long unsigned int', but argument 4 has type 'uint64_t'
> osm_vendor_mlx.c:746: warning: format '%llX' expects type 'long long unsigned int', but argument 4 has type 'uint64_t'
>
> osm_vendor_mlx_hca_sim.c: In function '__parse_ca_info_file':
> osm_vendor_mlx_hca_sim.c:268: warning: format '%016llx' expects type 'long long unsigned int', but argument 5 has type 'uint64_t'
>
> osm_vendor_mlx_dispatcher.c: In function '__osmv_dispatch_route':
> osm_vendor_mlx_dispatcher.c:208: warning: format '%llX' expects type 'long long unsigned int', but argument 4 has type 'uint64_t'
> osm_vendor_mlx_dispatcher.c:221: warning: format '%llX' expects type 'long long unsigned int', but argument 4 has type 'uint64_t'
> osm_vendor_mlx_dispatcher.c: In function '__osmv_dispatch_simple_mad':
> osm_vendor_mlx_dispatcher.c:276: warning: format '%llX' expects type 'long long unsigned int', but argument 4 has type 'long unsigned int'
> osm_vendor_mlx_dispatcher.c: In function '__osmv_dispatch_rmpp_mad':
> osm_vendor_mlx_dispatcher.c:331: warning: format '%llX' expects type 'long long unsigned int', but argument 4 has type 'uint64_t'
> osm_vendor_mlx_dispatcher.c: In function '__osmv_dispatch_rmpp_rcv':
> osm_vendor_mlx_dispatcher.c:570: warning: format '%llX' expects type 'long long unsigned int', but argument 4 has type 'uint64_t'
> osm_vendor_mlx_dispatcher.c:624: warning: format '%llX' expects type 'long long unsigned int', but argument 5 has type 'uint64_t'
> osm_vendor_mlx_dispatcher.c:629: warning: format '%llX' expects type 'long long unsigned int', but argument 4 has type 'long unsigned int'
> osm_vendor_mlx_dispatcher.c: In function '__osmv_dispatch_accept_seg':
> osm_vendor_mlx_dispatcher.c:661: warning: format '%llX' expects type 'long long unsigned int', but argument 4 has type 'uint64_t'
> osm_vendor_mlx_dispatcher.c:674: warning: format '%llX' expects type 'long long unsigned int', but argument 4 has type 'uint64_t'
>
> osm_vendor_mlx_sender.c: In function '__osmv_rmpp_send_segment':
> osm_vendor_mlx_sender.c:345: warning: format '%llX' expects type 'long long unsigned int', but argument 5 has type 'ib_net64_t'
>
> Signed-off-by: Hal Rosenstock <hal-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
> ---
Applied, thanks
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-06-03 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 19:03 [PATCH] opensm/libvendor: Fix compile warnings on 64 bit machines when building --with-osmv=sim Hal Rosenstock
[not found] ` <4DE7DE6A.9040100-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2011-06-03 10:48 ` Alex Netes [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=20110603104852.GF1098@calypso.voltaire.com \
--to=alexne-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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