From: Somya Anand <somyaanand214@gmail.com>
To: gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Somya Anand <somyaanand214@gmail.com>
Subject: [PATCH] Staging: Android: alarm-dev: Fixed a y2038 issue
Date: Wed, 1 Oct 2014 22:16:26 +0530 [thread overview]
Message-ID: <1412181986-4507-1-git-send-email-somyaanand214@gmail.com> (raw)
Fixed y2038 issue by replacing timespec with timespec64.
Signed-off-by: Somya Anand <somyaanand214@gmail.com>
---
drivers/staging/android/alarm-dev.c | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/android/alarm-dev.c b/drivers/staging/android/alarm-dev.c
index ff4b3e8..ba8acf4 100644
--- a/drivers/staging/android/alarm-dev.c
+++ b/drivers/staging/android/alarm-dev.c
@@ -14,6 +14,7 @@
*/
#include <linux/time.h>
+#include <linux/ktime.h>
#include <linux/module.h>
#include <linux/device.h>
#include <linux/miscdevice.h>
@@ -113,7 +114,7 @@ static void alarm_clear(enum android_alarm_type alarm_type)
}
static void alarm_set(enum android_alarm_type alarm_type,
- struct timespec *ts)
+ struct timespec64 *ts)
{
uint32_t alarm_type_mask = 1U << alarm_type;
unsigned long flags;
@@ -152,7 +153,7 @@ static int alarm_wait(void)
return rv;
}
-static int alarm_set_rtc(struct timespec *ts)
+static int alarm_set_rtc(struct timespec64 *ts)
{
struct rtc_time new_rtc_tm;
struct rtc_device *rtc_dev;
@@ -176,7 +177,7 @@ static int alarm_set_rtc(struct timespec *ts)
}
static int alarm_get_time(enum android_alarm_type alarm_type,
- struct timespec *ts)
+ struct timespec64 *ts)
{
int rv = 0;
@@ -199,7 +200,7 @@ static int alarm_get_time(enum android_alarm_type alarm_type,
}
static long alarm_do_ioctl(struct file *file, unsigned int cmd,
- struct timespec *ts)
+ struct timespec64 *ts)
{
int rv = 0;
unsigned long flags;
@@ -253,7 +254,7 @@ static long alarm_do_ioctl(struct file *file, unsigned int cmd,
static long alarm_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
{
- struct timespec ts;
+ struct timespec64 ts;
int rv;
switch (ANDROID_ALARM_BASE_CMD(cmd)) {
@@ -284,7 +285,7 @@ static long alarm_compat_ioctl(struct file *file, unsigned int cmd,
unsigned long arg)
{
- struct timespec ts;
+ struct timespec64 ts;
int rv;
switch (ANDROID_ALARM_BASE_CMD(cmd)) {
--
1.9.1
next reply other threads:[~2014-09-30 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 16:46 Somya Anand [this message]
2014-10-01 12:33 ` Dan Carpenter
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=1412181986-4507-1-git-send-email-somyaanand214@gmail.com \
--to=somyaanand214@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--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
all inboxes | Powered by JetHome®