From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Kent Overstreet <kmo@daterainc.com>,
linux-bcache@vger.kernel.org
Subject: [PATCH -next] bcache: fix btree printk format warning
Date: Wed, 04 Sep 2013 11:01:26 -0700 [thread overview]
Message-ID: <52277576.5020805@infradead.org> (raw)
In-Reply-To: <20130904181300.06fbf0698863cfaacf9fad9a@canb.auug.org.au>
From: Randy Dunlap <rdunlap@infradead.org>
Fix printk format warning on i386:
drivers/md/bcache/btree.c: In function 'bch_btree_node_read':
drivers/md/bcache/btree.c:259:8: warning: format '%lu' expects argument of type 'long unsigned int', but argument 3 has type 'size_t' [-Wformat]
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Kent Overstreet <kmo@daterainc.com>
Cc: linux-bcache@vger.kernel.org
---
drivers/md/bcache/btree.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20130904.orig/drivers/md/bcache/btree.c
+++ linux-next-20130904/drivers/md/bcache/btree.c
@@ -255,7 +255,7 @@ void bch_btree_node_read(struct btree *b
return;
err:
- bch_cache_set_error(b->c, "io error reading bucket %lu",
+ bch_cache_set_error(b->c, "io error reading bucket %zu",
PTR_BUCKET_NR(b->c, &b->key, 0));
}
next prev parent reply other threads:[~2013-09-04 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 8:13 linux-next: Tree for Sep 4 Stephen Rothwell
2013-09-04 17:46 ` linux-next: Tree for Sep 4 (netfilter: xt_TPROXY) Randy Dunlap
2013-09-04 21:09 ` Florian Westphal
2013-09-04 18:01 ` Randy Dunlap [this message]
2013-09-04 18:59 ` [PATCH -next] bcache: fix btree printk format warning Kent Overstreet
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=52277576.5020805@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=kmo@daterainc.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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