From: Jeremy Brown <mee@sgi.com>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.66
Date: Mon, 24 Mar 2003 16:16:44 -0800 [thread overview]
Message-ID: <20030325001644.GA35311@miine.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0303241524050.1741-100000@penguin.transmeta.com>
I encountered a minor build failure in fs/cramfs, which I was able to
fix with the following patch. I'm not sure if it's exactly the right
fix - does the original author really mean to have zeroes for those
values? Anyway, please consider applying to 2.5.66 if it's okay.
Jeremy Brown
--- linux-2.5.66/fs/cramfs/inode.c.orig 2003-03-24 16:01:07.000000000 -0800
+++ linux-2.5.66/fs/cramfs/inode.c 2003-03-24 16:09:18.000000000 -0800
@@ -43,6 +43,7 @@
static struct inode *get_cramfs_inode(struct super_block *sb, struct cramfs_inode * cramfs_inode)
{
struct inode * inode = new_inode(sb);
+ struct timespec zerotime = {0, 0};
if (inode) {
inode->i_mode = cramfs_inode->mode;
@@ -51,7 +52,7 @@
inode->i_blocks = (cramfs_inode->size - 1) / 512 + 1;
inode->i_blksize = PAGE_CACHE_SIZE;
inode->i_gid = cramfs_inode->gid;
- inode->i_mtime = inode->i_atime = inode->i_ctime = 0;
+ inode->i_mtime = inode->i_atime = inode->i_ctime = zerotime;
inode->i_ino = CRAMINO(cramfs_inode);
/* inode->i_nlink is left 1 - arguably wrong for directories,
but it's the best we can do without reading the directory
next prev parent reply other threads:[~2003-03-25 0:05 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 23:26 Linux 2.5.66 Linus Torvalds
2003-03-24 23:35 ` Larry McVoy
2003-03-25 0:14 ` Florin Iucha
2003-03-25 8:05 ` Rolf Eike Beer
2003-03-25 8:29 ` Marco Roeland
2003-03-25 0:16 ` Jeremy Brown [this message]
2003-03-25 0:22 ` Udo A. Steinberg
2003-03-25 0:30 ` Greg KH
2003-03-25 1:18 ` Udo A. Steinberg
2003-03-25 1:47 ` Greg KH
2003-03-25 4:18 ` CaT
2003-03-25 4:34 ` Greg KH
2003-03-25 5:56 ` CaT
2003-03-25 6:51 ` Greg KH
2003-03-25 7:22 ` CaT
2003-03-25 7:27 ` Greg KH
2003-03-25 0:53 ` John Cherry
2003-03-25 1:55 ` [REPRODUCABLE BUGS] " Toplica Tanaskovic
2003-03-25 3:19 ` James Simmons
2003-03-25 9:51 ` Toplica Tanaskovic
2003-03-26 20:24 ` James Simmons
2003-03-26 23:49 ` Torrey Hoffman
2003-03-27 0:20 ` James Simmons
2003-03-27 2:27 ` Joshua Kwan
2003-04-02 22:16 ` James Simmons
2003-04-03 1:02 ` Joshua Kwan
2003-04-03 3:59 ` James Simmons
2003-03-27 16:05 ` Toplica Tanaskovic
2003-03-26 2:53 ` Paweł Gołaszewski
2003-03-26 3:33 ` James Simmons
2003-03-26 11:00 ` [2.5 patch] fix sound/oss/mad16.c compile Adrian Bunk
2003-03-26 11:26 ` 2.5.66: compile problem with snd-ice1724 Adrian Bunk
2003-03-26 12:45 ` [2.5 patch] fix ipmi_devintf.c compilation Adrian Bunk
2003-03-26 14:36 ` Corey Minyard
-- strict thread matches above, loose matches on Subject: below --
2003-03-25 5:51 Linux 2.5.66 Andries.Brouwer
2003-03-26 10:45 ` Geert Uytterhoeven
2003-03-26 10:46 ` Geert Uytterhoeven
2003-03-25 7:40 Osamu Tomita
2003-03-26 11:52 Andries.Brouwer
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=20030325001644.GA35311@miine.engr.sgi.com \
--to=mee@sgi.com \
--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