From: swise@opengridcomputing.com (Steve Wise)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] infiniband: cxgb4: use %pR format string for printing resources
Date: Mon, 1 Feb 2016 10:45:04 -0600 [thread overview]
Message-ID: <025701d15d0f$e67ed760$b37c8620$@opengridcomputing.com> (raw)
In-Reply-To: <2278867.O0SM8nbQp0@wuerfel>
> Subject: [PATCH] infiniband: cxgb4: use %pR format string for printing resources
>
> The cxgb4 prints an MMIO resource using the "0x%x" and "%p" format
> strings on the length and start, respective, but that
> triggers a compiler warning when using a 64-bit resource_size_t
> on a 32-bit architecture:
>
> drivers/infiniband/hw/cxgb4/device.c: In function 'c4iw_rdev_open':
> drivers/infiniband/hw/cxgb4/device.c:807:7: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
> (void *)pci_resource_start(rdev->lldi.pdev, 2),
>
> This changes the format string to use %pR instead, which pretty-prints
> the resource, avoids the warning and is shorter.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> This is an old warning I see rarely on ARM randconfig builds.
Acked-by: Steve Wise <swise@opengridcomputing.com>
prev parent reply other threads:[~2016-02-01 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 16:42 [PATCH] infiniband: cxgb4: use %pR format string for printing resources Arnd Bergmann
2016-02-01 16:45 ` Steve Wise [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='025701d15d0f$e67ed760$b37c8620$@opengridcomputing.com' \
--to=swise@opengridcomputing.com \
--cc=linux-arm-kernel@lists.infradead.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).