From: "Randy.Dunlap" <rddunlap@osdl.org>
To: lkml <linux-kernel@vger.kernel.org>
Cc: akpm <akpm@osdl.org>
Subject: [PATCH] prevent minix_fs printk type warnings
Date: Fri, 22 Aug 2003 15:31:35 -0700 [thread overview]
Message-ID: <20030822153135.4b03f031.rddunlap@osdl.org> (raw)
Building on 64-bit (ia64) produces printk data type warnings
because ino_t is unsigned int there and unsigned long on x86.
--
~Randy
patch_name: minix_printk.patch
patch_version: 2003-08-22.15:25:32
author: Randy.Dunlap <rddunlap@osdl.org>
description: prevent printk() type warnings in minix fs
product: Linux
product_versions: 260-test3
diffstat: =
fs/minix/bitmap.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff -Naur ./fs/minix/bitmap.c~mnxtypes ./fs/minix/bitmap.c
--- ./fs/minix/bitmap.c~mnxtypes Fri Aug 8 21:39:25 2003
+++ ./fs/minix/bitmap.c Fri Aug 22 15:21:46 2003
@@ -116,7 +116,7 @@
if (!ino || ino > sbi->s_ninodes) {
printk("Bad inode number on dev %s: %ld is out of range\n",
- sb->s_id, ino);
+ sb->s_id, (unsigned long)ino);
return NULL;
}
ino--;
@@ -141,7 +141,7 @@
*bh = NULL;
if (!ino || ino > sbi->s_ninodes) {
printk("Bad inode number on dev %s: %ld is out of range\n",
- sb->s_id, ino);
+ sb->s_id, (unsigned long)ino);
return NULL;
}
ino--;
reply other threads:[~2003-08-22 23:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030822153135.4b03f031.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®