From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
dm-devel@redhat.com, akpm <akpm@linux-foundation.org>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-raid@vger.kernel.org
Subject: [PATCH -next] dm: fix dm-flakey printk warning
Date: Thu, 21 Jul 2011 16:10:47 -0700 [thread overview]
Message-ID: <20110721161047.8a62d89a.rdunlap@xenotime.net> (raw)
In-Reply-To: <20110721165542.7748c88a1d1e0b228c7fe3fa@canb.auug.org.au>
From: Randy Dunlap <rdunlap@xenotime.net>
Fix printk format warning for sector_t, which can be (unsigned)
long or long long.
drivers/md/dm-flakey.c:257: warning: format '%lu' expects type 'long unsigned int', but argument 7 has type 'sector_t'
Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
---
drivers/md/dm-flakey.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
--- linux-next-20110721.orig/drivers/md/dm-flakey.c
+++ linux-next-20110721/drivers/md/dm-flakey.c
@@ -255,10 +255,11 @@ static void corrupt_bio_data(struct bio
data[fc->corrupt_bio_byte - 1] = fc->corrupt_bio_value;
DMDEBUG("Corrupting data bio=%p by writing %u to byte %u "
- "(rw=%c bi_rw=%lu bi_sector=%lu cur_bytes=%u)\n",
+ "(rw=%c bi_rw=%lu bi_sector=%llu cur_bytes=%u)\n",
bio, fc->corrupt_bio_value, fc->corrupt_bio_byte,
(bio_data_dir(bio) == WRITE) ? 'w' : 'r',
- bio->bi_rw, bio->bi_sector, bio_bytes);
+ bio->bi_rw, (unsigned long long)bio->bi_sector,
+ bio_bytes);
}
}
next prev parent reply other threads:[~2011-07-21 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110721165542.7748c88a1d1e0b228c7fe3fa@canb.auug.org.au>
2011-07-21 21:56 ` linux-next: Tree for July 21 (drivers/md/dm-raid) Randy Dunlap
2011-07-21 22:10 ` NeilBrown
2011-07-22 1:14 ` [dm-devel] " Alasdair G Kergon
2011-07-21 23:10 ` Randy Dunlap [this message]
2011-07-22 16:25 ` [dm-devel] [PATCH -next] dm: fix dm-flakey printk warning Alasdair G Kergon
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=20110721161047.8a62d89a.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@linux-foundation.org \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--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).