Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751543AbdISQqj (ORCPT ); Tue, 19 Sep 2017 12:46:39 -0400 Received: from mail-wr0-f179.google.com ([209.85.128.179]:54834 "EHLO mail-wr0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750973AbdISQqh (ORCPT ); Tue, 19 Sep 2017 12:46:37 -0400 X-Google-Smtp-Source: AOwi7QAQ/tGcdG3vkUkBpEYGkWjH6Dq06S2aK2v3iDo1PgJlUcBihXPDPADxpIuHft1/dfkyH4B5ww== Date: Tue, 19 Sep 2017 18:46:15 +0200 From: Richard Cochran To: Miroslav Lichvar Cc: Richard Cochran , netdev@vger.kernel.org, Andre Guedes , Henrik Austad , linux-kernel@vger.kernel.org, Jesus Sanchez-Palencia , intel-wired-lan@lists.osuosl.org, John Stultz , Thomas Gleixner , Anna-Maria Gleixner , David Miller Subject: Re: [PATCH RFC V1 net-next 0/6] Time based packet transmission Message-ID: <20170919164615.mfv77pxuuyqc4zq4@localhost> References: <20170919144302.GB4347@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170919144302.GB4347@localhost> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 274 Lines: 8 On Tue, Sep 19, 2017 at 04:43:02PM +0200, Miroslav Lichvar wrote: > If I understand it correctly, this also allows us to make a PTP/NTP > "one-step" clock with HW that doesn't support it directly. Cool, yeah, I hadn't thought of that, but it would work... Thanks, Richard