From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Tina Ruchandani <ruchandani.tina@gmail.com>,
Arnd Bergmann <arnd@arndb.de>
Cc: y2038@lists.linaro.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fbdev: radeon: Remove 'struct timeval' usage
Date: Thu, 20 Aug 2015 07:51:26 +0000 [thread overview]
Message-ID: <55D586FE.6070303@ti.com> (raw)
In-Reply-To: <20150525040716.GA4448@tinar>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
Hi Tina,
On 25/05/15 07:07, Tina Ruchandani wrote:
> 'struct timeval' uses a 32-bit representation for the
> seconds field which will overflow in the year 2038 and beyond.
> This patch replaces the usage of 'struct timeval' with
> ktime_t which uses a 64-bit time representation and does not
> suffer from the y2038 problem. This patch is part of a larger
> effort to remove all instances of 'struct timeval', 'struct
> timespec', time_t and other 32-bit timekeeping variables
> from the kernel.
> The patch also replaces the use of real time (do_gettimeofday)
> with monotonic time (ktime_get).
>
> Signed-off-by: Tina Ruchandani <ruchandani.tina@gmail.com>
I had dropped this from 4.2 as there were issues reported, but forgot to
write a mail about it...
Can you send a updated patch with the issues fixed?
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-08-20 7:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 4:19 [PATCH] fbdev: radeon: Remove 'struct timeval' usage Tina Ruchandani
2015-06-03 11:59 ` Tomi Valkeinen
2015-06-05 4:40 ` Dave Airlie
2015-06-05 7:55 ` Tina Ruchandani
2015-06-05 21:12 ` [Y2038] " Arnd Bergmann
2015-08-20 7:51 ` Tomi Valkeinen [this message]
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=55D586FE.6070303@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--cc=ruchandani.tina@gmail.com \
--cc=y2038@lists.linaro.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;
as well as URLs for NNTP newsgroup(s).