[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1368616680.19370.4.camel@dabdike>
Date: Wed, 15 May 2013 07:18:00 -0400
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Gu Zheng <guz.fnst@...fujitsu.com>
Cc: John Stultz <john.stultz@...aro.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-scsi@...r.kernel.org
Subject: Re: [PATCH 1/2] Kernel/time: Introduce a new timestamp function
local_time_seconds()
On Wed, 2013-05-15 at 11:32 +0800, Gu Zheng wrote:
> On 05/14/2013 11:57 PM, John Stultz wrote:
>
> > On 05/14/2013 12:45 AM, Gu Zheng wrote:
> >> From 18072c1c3506a7e37ee485307a2c343efe5af4d0 Mon Sep 17 00:00:00 2001
> >> From: Gu Zheng <guz.fnst@...fujitsu.com>
> >> Date: Mon, 13 May 2013 15:45:24 +0900
> >> Subject: [PATCH 1/2] Kernel/time: Introduce a new timestamp function local_time_seconds()
> >>
> >> Introduce a new timestamp function local_time_seconds() to hide the conversion of system time in UTC to local time seconds.
> >
> > So, why is this useful/needed?
>
> Hi John,
> There are some subsystems use local time seconds as a timestamp,
> such as scsi(refer
> to:http://www.spinics.net/lists/linux-scsi/msg66089.html),
> and so do many out-of-kernel-tree code I think.
I don't think the 3ware drivers, which are the only ones that do this
actually care. I think jiffies to seconds would suit the event
timestamps equally well, so I don't really see a need to make this a
formal kernel export given that it's only a single driver family in the
entirety of the kernel.
James
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists