netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: amsfield22@gmail.com
Cc: mac@melware.de, isdn@linux-pingi.de, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, y2038@lists.linaro.org
Subject: Re: [RESEND PATCH v3] isdn: divamnt: use y2038-safe ktime_get_ts64() for trace data timestamps
Date: Thu, 18 Feb 2016 11:10:07 -0500 (EST)	[thread overview]
Message-ID: <20160218.111007.1949710047777164403.davem@davemloft.net> (raw)
In-Reply-To: <1455777311-3190-1-git-send-email-amsfield22@gmail.com>

From: Alison Schofield <amsfield22@gmail.com>
Date: Wed, 17 Feb 2016 22:35:11 -0800

> divamnt stores a start_time at module init and uses it to calculate
> elapsed time. The elapsed time, stored in secs and usecs, is part of
> the trace data the driver maintains for the DIVA Server ISDN cards.
> No change to the format of that time data is required.
> 
> To avoid overflow on 32-bit systems use ktime_get_ts64() to return
> the elapsed monotonic time since system boot.
> 
> This is a change from real to monotonic time. Since the driver only
> stores elapsed time, monotonic time is sufficient and more robust
> against real time clock changes. These new monotonic values can be
> more useful for debugging because they can be easily compared to
> other monotonic timestamps.
> 
> Note elaspsed time values will now start at system boot time rather
> than module load time, so they will differ slightly from previously
> reported values.
> 
> Remove declaration and init of previously unused time constants:
> start_sec, start_usec.
> 
> Signed-off-by: Alison Schofield <amsfield22@gmail.com>
> Reviewed-by: Arnd Bergmann <arnd@arndb.de>

Applied to net-next, thanks.

      reply	other threads:[~2016-02-18 16:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20151120182307.GA3513@d830.WORKGROUP>
2016-01-15 16:51 ` [PATCH v3] isdn: divamnt: use y2038-safe ktime_get_ts64() for trace data timestamps Alison Schofield
2016-01-18  0:27   ` David Miller
2016-02-18  6:35 ` [RESEND PATCH " Alison Schofield
2016-02-18 16:10   ` David Miller [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=20160218.111007.1949710047777164403.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=amsfield22@gmail.com \
    --cc=isdn@linux-pingi.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mac@melware.de \
    --cc=netdev@vger.kernel.org \
    --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).