On Wednesday 28 January 2015 09:53:49 Steven Rostedt wrote:
> On Wed, 28 Jan 2015 19:46:11 +0530
> Tina Ruchandani <[email protected]> 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 <[email protected]>
> > Suggested-by: Steven Rostedt <[email protected]>
> > Signed-off-by: Tina Ruchandani <[email protected]>
> > ---
> > 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
