linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Beregalov <a.beregalov@gmail.com>
To: tytso@mit.edu, linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH next] ext4: fix printk format warning in inode.c
Date: Tue, 31 Mar 2009 15:54:51 +0400	[thread overview]
Message-ID: <20090331115451.GA3475@orion> (raw)

fs/ext4/inode.c:385: warning: format '%u' expects type 'unsigned int', but argument 7 has type 'long int'

Signed-off-by: Alexander Beregalov <a.beregalov@gmail.com>
---

 fs/ext4/inode.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
index 1d37d14..2fda129 100644
--- a/fs/ext4/inode.c
+++ b/fs/ext4/inode.c
@@ -382,7 +382,7 @@ static int __ext4_check_blockref(const char *function, struct inode *inode,
 				   "block reference %u >= max (%u) "
 				   "in inode #%lu, offset=%u",
 				   *bref, maxblocks,
-				   inode->i_ino, bref-p);
+				   inode->i_ino, (unsigned)(bref-p));
  			return -EIO;
  		}
 		bref++;

             reply	other threads:[~2009-03-31 11:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31 11:54 Alexander Beregalov [this message]
2009-03-31 12:37 ` [PATCH next] ext4: fix printk format warning in inode.c Theodore Tso

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=20090331115451.GA3475@orion \
    --to=a.beregalov@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).