From: Richard Cochran <richardcochran@gmail.com>
To: Daniel Walker <danielwa@cisco.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"xe-kernel@external.cisco.com" <xe-kernel@external.cisco.com>,
"Shabeena Shabeena -X (sshabeen - ARICENT TECHNOLOGIES
MAURIITIUS LIMITED at Cisco)" <sshabeen@cisco.com>
Subject: Re: ptp
Date: Wed, 7 Sep 2016 23:12:23 +0200 [thread overview]
Message-ID: <20160907211223.GA31741@localhost.localdomain> (raw)
In-Reply-To: <85389e04-76ad-9a19-2a33-d49a9bdd8452@cisco.com>
On Wed, Sep 07, 2016 at 01:55:19PM -0700, Daniel Walker wrote:
> So the code only allows second granularity negative updates,
No.
> or the seconds
> component is the only part which needs to actually be negative ?
Yes.
See the function, clockadj_step, in linuxptp/clockadj.c for a working
user space example.
Thanks,
Richard
prev parent reply other threads:[~2016-09-07 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d1b2b740-8cc6-bf4a-722b-7b323fb0c7c0@cisco.com>
2016-09-07 20:48 ` ptp Richard Cochran
2016-09-07 20:55 ` ptp Daniel Walker
2016-09-07 21:12 ` Richard Cochran [this message]
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=20160907211223.GA31741@localhost.localdomain \
--to=richardcochran@gmail.com \
--cc=danielwa@cisco.com \
--cc=netdev@vger.kernel.org \
--cc=sshabeen@cisco.com \
--cc=xe-kernel@external.cisco.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).