public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Kelly <akelly@on-demand-tech.com>
To: viro@math.psu.edu, linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: [PATCH] linux-2.5.66/fs/cramfs/inode.c typecheck - int vs. struct
Date: Tue, 25 Mar 2003 23:45:10 -0600	[thread overview]
Message-ID: <3E813E66.1060802@on-demand-tech.com> (raw)

Very minor change. GCC now does more type checking, so This just zeros a 
timespec struct
so that i_mtime, etc will match types.

gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)
compiling linux-2.5.66

 -Adam

--- inode.c.orig        2003-03-25 22:50:17.000000000 -0600
+++ inode.c     2003-03-25 23:00:50.000000000 -0600
@@ -44,6 +44,8 @@
 {
        struct inode * inode = new_inode(sb);
 
+       const struct timespec zero_timespec = {0};
+
        if (inode) {
                inode->i_mode = cramfs_inode->mode;
                inode->i_uid = cramfs_inode->uid;
@@ -51,7 +53,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 = 
zero_timespec;
                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  


                 reply	other threads:[~2003-03-26  5:27 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=3E813E66.1060802@on-demand-tech.com \
    --to=akelly@on-demand-tech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=viro@math.psu.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