From: Adrian Bunk <bunk@fs.tum.de>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org
Subject: [2.5 patch] fix compile breakage in fs/ after nanosecond stat timefields patch
Date: Mon, 18 Nov 2002 12:21:09 +0100 [thread overview]
Message-ID: <20021118112108.GA5420@fs.tum.de> (raw)
Hi Andi,
the patch below fixes the following compile errors in 2.5.48:
<-- snip -->
..
gcc -Wp,-MD,fs/adfs/.inode.o.d -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -Iarch/i386/mach-generic -nostdinc -iwithprefix include -DKBUILD_BASENAME=inode -DKBUILD_MODNAME=adfs -c -o fs/adfs/inode.o fs/adfs/inode.c
fs/adfs/inode.c: In function `adfs_adfs2unix_time':
fs/adfs/inode.c:188: incompatible types in return
make[2]: *** [fs/adfs/inode.o] Error 1
...
gcc -Wp,-MD,fs/afs/.vlclient.o.d -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -Iarch/i386/mach-generic -nostdinc -iwithprefix include -DKBUILD_BASENAME=vlclient -DKBUILD_MODNAME=kafs -c -o fs/afs/vlclient.o fs/afs/vlclient.c
fs/afs/vlclient.c: In function `afs_rxvl_get_entry_by_id_async2':
fs/afs/vlclient.c:587: incompatible types in assignment
make[2]: *** [fs/afs/vlclient.o] Error 1
...
gcc -Wp,-MD,fs/jffs2/.fs.o.d -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -Iarch/i386/mach-generic -nostdinc -iwithprefix include -DKBUILD_BASENAME=fs -DKBUILD_MODNAME=jffs2 -c -o fs/jffs2/fs.o fs/jffs2/fs.c
fs/jffs2/fs.c: In function `jffs2_new_inode':
fs/jffs2/fs.c:257: incompatible types in assignment
make[2]: *** [fs/jffs2/fs.o] Error 1
<-- snip -->
Please check whether the patch is correct.
TIA
Adrian
--- linux-2.5.48/fs/adfs/inode.c.old 2002-11-18 11:29:15.000000000 +0100
+++ linux-2.5.48/fs/adfs/inode.c 2002-11-18 11:30:43.000000000 +0100
@@ -185,7 +185,7 @@
unsigned int high, low;
if (ADFS_I(inode)->stamped == 0)
- return CURRENT_TIME;
+ return get_seconds();
high = ADFS_I(inode)->loadaddr << 24;
low = ADFS_I(inode)->execaddr;
--- linux-2.5.48/fs/afs/vlclient.c.old 2002-11-18 11:36:13.000000000 +0100
+++ linux-2.5.48/fs/afs/vlclient.c 2002-11-18 11:37:41.000000000 +0100
@@ -584,7 +584,7 @@
#endif
/* success */
- entry->ctime = CURRENT_TIME;
+ entry->ctime = get_seconds();
ret = 0;
goto done;
}
--- linux-2.5.48/fs/jffs2/fs.c.old 2002-11-18 11:49:23.000000000 +0100
+++ linux-2.5.48/fs/jffs2/fs.c 2002-11-18 11:55:43.000000000 +0100
@@ -253,7 +253,8 @@
inode->i_mode = ri->mode;
inode->i_gid = ri->gid;
inode->i_uid = ri->uid;
- inode->i_atime = inode->i_ctime = inode->i_mtime =
+ inode->i_atime.tv_sec = inode->i_ctime.tv_sec =
+ inode->i_mtime.tv_sec =
ri->atime = ri->mtime = ri->ctime = get_seconds();
inode->i_blksize = PAGE_SIZE;
inode->i_blocks = 0;
next reply other threads:[~2002-11-18 11:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-18 11:21 Adrian Bunk [this message]
2002-11-18 13:58 ` [2.5 patch] fix compile breakage in fs/ after nanosecond stat timefields patch Andi Kleen
2002-11-18 14:50 ` Holger Waechtler
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=20021118112108.GA5420@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=ak@muc.de \
--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