[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VeJWuPyEZkzgbxZZriCaDkX9+ViHJ-X1NO0tofdDOMZLA@mail.gmail.com>
Date: Tue, 19 Jun 2018 23:39:42 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Pavel Tatashin <pasha.tatashin@...cle.com>
Cc: Steven Sistare <steven.sistare@...cle.com>,
Daniel Jordan <daniel.m.jordan@...cle.com>,
Russell King - ARM Linux <linux@...linux.org.uk>,
Martin Schwidefsky <schwidefsky@...ibm.com>,
Heiko Carstens <heiko.carstens@...ibm.com>,
John Stultz <john.stultz@...aro.org>,
Stephen Boyd <sboyd@...eaurora.org>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" <x86@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Dou Liyang <douly.fnst@...fujitsu.com>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>, prarit@...hat.com,
Feng Tang <feng.tang@...el.com>,
Petr Mladek <pmladek@...e.com>,
One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
Subject: Re: [PATCH v10 3/7] x86/time: read_boot_clock64() implementation
On Tue, Jun 19, 2018 at 5:23 PM, Pavel Tatashin
<pasha.tatashin@...cle.com> wrote:
>> > > + *ts = (struct timespec64){0, 0};
>>
>> I dunno if additional variable would be better for readability, like
>>
>> struct timespec64 null_ts = {0,0};
>
> I don't mind adding ts_null, but I think, as-is ok here,
Actually I meant presicely null_ts, and the reason why is that alias
is much easy to parse to get the idea, than to read entire "struct bla
bla bla".
But again, this is my personal point of view.
>
>> ...
>> *ts = null_ts;
>>
>> > > + else
>> > > + *ts = ns_to_timespec64(ns_now - ns_boot);
>>
>> But I'm fine as long as Thomas is okay with this code.
> Thank you for the review!
You're welcome!
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists