The patch titled
ext2: fix format string compile warning (ino_t)
has been added to the -mm tree. Its filename is
ext2-fix-format-string-compile-warning-ino_t.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: ext2: fix format string compile warning (ino_t)
From: Heiko Carstens <heiko.carstens@xxxxxxxxxx>
Unlike on most other architectures ino_t is an unsigned int on s390. So
add an explicit cast to avoid this compile warning:
fs/ext2/namei.c: In function 'ext2_lookup':
fs/ext2/namei.c:73: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'ino_t'
Signed-off-by: Heiko Carstens <heiko.carstens@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/ext2/namei.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN fs/ext2/namei.c~ext2-fix-format-string-compile-warning-ino_t fs/ext2/namei.c
--- a/fs/ext2/namei.c~ext2-fix-format-string-compile-warning-ino_t
+++ a/fs/ext2/namei.c
@@ -70,7 +70,7 @@ static struct dentry *ext2_lookup(struct
if (PTR_ERR(inode) == -ESTALE) {
ext2_error(dir->i_sb, __func__,
"deleted inode referenced: %lu",
- ino);
+ (unsigned long) ino);
return ERR_PTR(-EIO);
} else {
return ERR_CAST(inode);
_
Patches currently in -mm which might be from heiko.carstens@xxxxxxxxxx are
linux-next.patch
poll-select-avoid-arithmetic-overflow-in-__estimate_accuracy.patch
ext2-fix-format-string-compile-warning-ino_t.patch
nilfs2-fix-format-string-compile-warning-ino_t.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
