From: Arnd Bergmann <arnd@arndb.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Tina Ruchandani <ruchandani.tina@gmail.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH v4] trace: Use 64-bit timekeeping
Date: Wed, 28 Jan 2015 15:55:39 +0100 [thread overview]
Message-ID: <13699348.kjuUqHkb9Z@wuerfel> (raw)
In-Reply-To: <20150128095349.6a3537a2@gandalf.local.home>
On Wednesday 28 January 2015 09:53:49 Steven Rostedt wrote:
> On Wed, 28 Jan 2015 19:46:11 +0530
> Tina Ruchandani <ruchandani.tina@gmail.com> wrote:
>
> > The ring_buffer_producer uses 'struct timeval' to measure
> > its start and end times. 'struct timeval' on 32-bit systems
> > will have its tv_sec value overflow in year 2038 and beyond.
> > This patch replaces struct timeval with 'ktime_t' which uses
> > 64-bit representation for nanoseconds.
> >
> > Suggested-by: Arnd Bergmann <arnd@arndb.de>
> > Suggested-by: Steven Rostedt <rostedt@goodmis.org>
> > Signed-off-by: Tina Ruchandani <ruchandani.tina@gmail.com>
> > ---
> > Changes in v4:
> > - Fix typo in commit message.
> > - Avoid typecast to 'long long' by defining RUN_TIME as '10ULL'
> > instead of '10'.
>
> Although I have not tested this, this patch looks fine to me. Is this
> going to go through some cleanup tree or should I just pull it?
>
Please apply it to your tree.
Arnd
next prev parent reply other threads:[~2015-01-29 4:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 14:16 Tina Ruchandani
2015-01-28 14:53 ` Steven Rostedt
2015-01-28 14:55 ` Arnd Bergmann [this message]
2015-01-28 15:05 ` Steven Rostedt
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=13699348.kjuUqHkb9Z@wuerfel \
--to=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=ruchandani.tina@gmail.com \
/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®