[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87y2nub3v9.fsf@osv.gnss.ru>
Date: Wed, 08 Jul 2020 15:14:34 +0300
From: Sergey Organov <sorganov@...il.com>
To: Richard Cochran <richardcochran@...il.com>
Cc: Vladimir Oltean <olteanv@...il.com>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, Fugang Duan <fugang.duan@....com>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>
Subject: Re: [PATCH 3/5] net: fec: initialize clock with 0 rather than
current kernel time
Richard Cochran <richardcochran@...il.com> writes:
> On Tue, Jul 07, 2020 at 08:56:41PM +0300, Sergey Organov wrote:
>> It won't. Supposedly it'd force clock (that doesn't tick by default and
>> stays at 0) to start ticking.
>
> No existing clockid_t has this behavior. Consider CLOCK_REALTIME or
> CLOCK_MONOTONIC.
>
> The PHC must act the same as the other POSIX clocks.
Yeah, that's a good argument!
Thanks,
-- Sergey
Powered by blists - more mailing lists