From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1754221AbcK2QOG (ORCPT <rfc822;w@1wt.eu>);
        Tue, 29 Nov 2016 11:14:06 -0500
Received: from Galois.linutronix.de ([146.0.238.70]:51659 "EHLO
        Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751347AbcK2QN6 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 29 Nov 2016 11:13:58 -0500
Date: Tue, 29 Nov 2016 17:11:15 +0100 (CET)
From: Thomas Gleixner <tglx@linutronix.de>
To: Joel Fernandes <joelaf@google.com>
cc: Ingo Molnar <mingo@kernel.org>, John Stultz <john.stultz@linaro.org>,
        lkml <linux-kernel@vger.kernel.org>,
        Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@redhat.com>,
        Richard Cochran <richardcochran@gmail.com>,
        Prarit Bhargava <prarit@redhat.com>
Subject: Re: [PATCH 7/7] trace: Update documentation for mono, mono_raw and
 boot clock
In-Reply-To: <CAJWu+opzu=J0=6FJvVQUWuQ1frzcJxRtADxp4ULZ_e1pm6bFUA@mail.gmail.com>
Message-ID: <alpine.DEB.2.20.1611291710490.4358@nanos>
References: <1480372524-15181-1-git-send-email-john.stultz@linaro.org> <1480372524-15181-8-git-send-email-john.stultz@linaro.org> <20161129072651.GD29412@gmail.com> <CAJWu+opzu=J0=6FJvVQUWuQ1frzcJxRtADxp4ULZ_e1pm6bFUA@mail.gmail.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, 29 Nov 2016, Joel Fernandes wrote:
> On Mon, Nov 28, 2016 at 11:26 PM, Ingo Molnar <mingo@kernel.org> wrote:
> >
> > * John Stultz <john.stultz@linaro.org> wrote:
> >
> >> +       boot: This is the boot clock (CLOCK_BOOTTIME) and is based on the
> >> +             fast monotonic clock, but also accounts for time spent in
> >> +             suspend. Since the clock access is designed for use in
> >> +             tracing in the suspend path, some side effects are possible
> >> +             if clock is accessed after the suspend time is accounted before
> >> +             the fast mono clock is updated. In this case, the clock update
> >> +             appears to happen slightly sooner than it normally would have.
> >> +             Also on 32-bit systems, its possible that the 64-bit boot offset
> >> +             sees a partial update. These effects are rare and post
> >> +             processing should be able to handle them. See comments on
> >> +             ktime_get_boot_fast_ns function for more information.
> >
> > s/its possible/it's possible
> > s/comments on ktime_get_boost_fast_ns function/comments in the ktime_get_boost_fast_ns() function
> >
> 
> Thanks, I'll fix these up and repost.

Don't bother. I have fixed it up locally already.

Thanks,

	tglx