From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Or Gerlitz <ogerlitz@mellanox.com>,
Roi Dayan <roid@mellanox.com>,
linux-rdma@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Roland Dreier <roland@kernel.org>,
Sean Hefty <sean.hefty@intel.com>,
Hal Rosenstock <hal.rosenstock@gmail.com>
Subject: [PATCH -next] infiniband: fix iser_verbs.c format warning
Date: Fri, 28 Mar 2014 14:03:40 -0700 [thread overview]
Message-ID: <5335E3AC.8080401@infradead.org> (raw)
In-Reply-To: <20140328180950.322d12920ce31e0ad3dace59@canb.auug.org.au>
From: Randy Dunlap <rdunlap@infradead.org>
Fix pr_err (printk) format warning:
drivers/infiniband/ulp/iser/iser_verbs.c:1181:4: warning: format '%lx' expects argument of type 'long unsigned int', but argument 3 has type 'sector_t' [-Wformat]
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Or Gerlitz <ogerlitz@mellanox.com>
Cc: Roi Dayan <roid@mellanox.com>
Cc: linux-rdma@vger.kernel.org
---
drivers/infiniband/ulp/iser/iser_verbs.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
--- linux-next-20140328.orig/drivers/infiniband/ulp/iser/iser_verbs.c
+++ linux-next-20140328/drivers/infiniband/ulp/iser/iser_verbs.c
@@ -1178,9 +1178,10 @@ u8 iser_check_task_pi_status(struct iscs
do_div(sector_off, sector_size + 8);
*sector = scsi_get_lba(iser_task->sc) + sector_off;
- pr_err("PI error found type %d at sector %lx "
+ pr_err("PI error found type %d at sector %llx "
"expected %x vs actual %x\n",
- mr_status.sig_err.err_type, *sector,
+ mr_status.sig_err.err_type,
+ (unsigned long long)*sector,
mr_status.sig_err.expected,
mr_status.sig_err.actual);
prev parent reply other threads:[~2014-03-28 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 7:09 linux-next: Tree for Mar 28 Stephen Rothwell
2014-03-28 18:26 ` linux-next: Tree for Mar 28 (qlcnic) Randy Dunlap
2014-03-29 9:11 ` Shahed Shaikh
2014-03-28 21:03 ` Randy Dunlap [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=5335E3AC.8080401@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=hal.rosenstock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=roid@mellanox.com \
--cc=roland@kernel.org \
--cc=sean.hefty@intel.com \
--cc=sfr@canb.auug.org.au \
/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).