From: David Howells <dhowells@redhat.com>
To: Tina Ruchandani <ruchandani.tina@gmail.com>
Cc: dhowells@redhat.com, linux-afs@lists.infradead.org,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] afs: Migrate to 64-bit timekeeping
Date: Wed, 11 Feb 2015 11:26:06 +0000 [thread overview]
Message-ID: <20540.1423653966@warthog.procyon.org.uk> (raw)
In-Reply-To: <20150129060507.GA3437@tinar>
Tina Ruchandani <ruchandani.tina@gmail.com> wrote:
> This patchset is an attempt to port afs's timekeeping
> variables from time_t type to time64_t. AFS uses
> get_seconds to store real (wall clock) time in seconds.
> The time returned by get_seconds() will overflow on 32-bit systems
> in year 2106 and beyond.
> This patchset replaces the usage with ktime_get_real_seconds.
> Fields that propagate to the inode (mtime_client, mtime_server,
> creation) remain untouched, as the inode timestamps are only 32bit.
I've applied these to my branch.
David
next prev parent reply other threads:[~2015-02-11 11:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 6:05 Tina Ruchandani
2015-02-11 11:26 ` David Howells [this message]
2015-02-11 12:52 ` David Howells
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=20540.1423653966@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=arnd@arndb.de \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ruchandani.tina@gmail.com \
/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
Powered by JetHome