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 S1752142AbcK2QKj (ORCPT <rfc822;w@1wt.eu>);
        Tue, 29 Nov 2016 11:10:39 -0500
Received: from mail-vk0-f42.google.com ([209.85.213.42]:35374 "EHLO
        mail-vk0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1750820AbcK2QKb (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 29 Nov 2016 11:10:31 -0500
MIME-Version: 1.0
In-Reply-To: <20161129072651.GD29412@gmail.com>
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>
From: Joel Fernandes <joelaf@google.com>
Date: Tue, 29 Nov 2016 08:10:30 -0800
Message-ID: <CAJWu+opzu=J0=6FJvVQUWuQ1frzcJxRtADxp4ULZ_e1pm6bFUA@mail.gmail.com>
Subject: Re: [PATCH 7/7] trace: Update documentation for mono, mono_raw and
 boot clock
To: Ingo Molnar <mingo@kernel.org>
Cc: John Stultz <john.stultz@linaro.org>,
        lkml <linux-kernel@vger.kernel.org>,
        Steven Rostedt <rostedt@goodmis.org>,
        Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@redhat.com>,
        Richard Cochran <richardcochran@gmail.com>,
        Prarit Bhargava <prarit@redhat.com>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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.

Regards,
Joel

> Thanks,
>
>         Ingo