From: Prarit Bhargava <prarit@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
John Stultz <john.stultz@linaro.org>,
Stephen Boyd <sboyd@codeaurora.org>
Subject: Re: [PATCH 1/3 v11] time: Make fast functions return 0 before timekeeping is initialized
Date: Fri, 15 Sep 2017 09:42:19 -0400 [thread overview]
Message-ID: <9a2f5705-9617-6a27-2a96-8750c78fb451@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1709051414400.1900@nanos>
On 09/05/2017 08:15 AM, Thomas Gleixner wrote:
> On Tue, 5 Sep 2017, Prarit Bhargava wrote:
>> +static struct tk_fast tk_fast_mono ____cacheline_aligned = {
>> + .base = {
>> + (struct tk_read_base){
>> + .clock = &dummy_clock,
>> + },
>> + (struct tk_read_base){
>> + .clock = &dummy_clock,
>> + },
>> + },
>> +};
>
> http://lkml.kernel.org/r/alpine.DEB.2.20.1708281658370.1867@nanos
>
> Sigh
Oof ... sorry tglx. I missed that email :( My apologies. I'll fix that,
retest, and resend.
P.
>
> tglx
>
next prev parent reply other threads:[~2017-09-15 13:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 12:06 [PATCH 0/3 v11] printk: Add new timestamps Prarit Bhargava
2017-09-05 12:06 ` [PATCH 1/3 v11] time: Make fast functions return 0 before timekeeping is initialized Prarit Bhargava
2017-09-05 12:15 ` Thomas Gleixner
2017-09-15 13:42 ` Prarit Bhargava [this message]
2017-09-05 12:06 ` [PATCH 2/3 v11] timekeeping: Provide NMI safe access to clock realtime Prarit Bhargava
2017-09-05 12:06 ` [PATCH 3/3 v11] printk: Add monotonic, boottime, and realtime timestamps Prarit Bhargava
2017-09-13 18:30 ` Mark Salyzyn
2017-09-15 13:28 ` Petr Mladek
2017-09-15 14:29 ` Mark Salyzyn
2017-09-17 10:46 ` Sergey Senozhatsky
2017-09-19 11:52 ` Prarit Bhargava
2017-09-15 14:40 ` Prarit Bhargava
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=9a2f5705-9617-6a27-2a96-8750c78fb451@redhat.com \
--to=prarit@redhat.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@codeaurora.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.