public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Gu Zheng <guz.fnst@cn.fujitsu.com>
Cc: John Stultz <john.stultz@linaro.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/2] Kernel/time: Introduce a new timestamp function local_time_seconds()
Date: Wed, 15 May 2013 07:18:00 -0400	[thread overview]
Message-ID: <1368616680.19370.4.camel@dabdike> (raw)
In-Reply-To: <519301D8.2030502@cn.fujitsu.com>

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@cn.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



      reply	other threads:[~2013-05-15 11:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14  7:45 [PATCH 1/2] Kernel/time: Introduce a new timestamp function local_time_seconds() Gu Zheng
2013-05-14 15:57 ` John Stultz
2013-05-15  3:32   ` Gu Zheng
2013-05-15 11:18     ` James Bottomley [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=1368616680.19370.4.camel@dabdike \
    --to=james.bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=guz.fnst@cn.fujitsu.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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