From: SeongJae Park <sj38.park@gmail.com>
To: trivial@kernel.org, ian.campbell@citrix.com, wei.liu2@citrix.com
Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH] ixen-netback: fix trivial printf format build warning
Date: Wed, 26 Mar 2014 12:56:50 +0900 [thread overview]
Message-ID: <1395806210-23528-1-git-send-email-sj38.park@gmail.com> (raw)
Fix following trivial build warning:
drivers/net/xen-netback/netback.c: In function ‘xenvif_tx_dealloc_action’:
drivers/net/xen-netback/netback.c:1585:8: warning:
format ‘%x’ expects argument of type
‘unsigned int’, but argument 3 has type ‘long int’ [-Wformat=]
gop - vif->tx_unmap_ops, ret);
^
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
drivers/net/xen-netback/netback.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/xen-netback/netback.c b/drivers/net/xen-netback/netback.c
index 5a8c4a4..90001b3 100644
--- a/drivers/net/xen-netback/netback.c
+++ b/drivers/net/xen-netback/netback.c
@@ -1574,7 +1574,7 @@ static inline void xenvif_tx_dealloc_action(struct xenvif *vif)
vif->pages_to_unmap,
gop - vif->tx_unmap_ops);
if (ret) {
- netdev_err(vif->dev, "Unmap fail: nr_ops %x ret %d\n",
+ netdev_err(vif->dev, "Unmap fail: nr_ops %lx ret %d\n",
gop - vif->tx_unmap_ops, ret);
for (i = 0; i < gop - vif->tx_unmap_ops; ++i) {
if (gop[i].status != GNTST_okay)
--
1.8.3.2
next reply other threads:[~2014-03-26 3:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 3:56 SeongJae Park [this message]
2014-03-26 10:09 ` [PATCH] ixen-netback: fix trivial printf format build warning Ian Campbell
2014-03-26 10:34 ` SeongJae Park
2014-03-26 18:46 ` David Miller
2014-03-26 18:51 ` SeongJae Park
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=1395806210-23528-1-git-send-email-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--cc=ian.campbell@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=trivial@kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).