From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Cochran Subject: Re: [Intel-wired-lan] [RFC v2 net-next 01/10] net: Add a new socket option for a future transmit time. Date: Thu, 18 Jan 2018 09:13:35 -0800 Message-ID: <20180118171335.bhyl76wobdffedho@localhost> References: <20180117230621.26074-1-jesus.sanchez-palencia@intel.com> <20180117230621.26074-2-jesus.sanchez-palencia@intel.com> <20180118084227.GL1175@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jesus Sanchez-Palencia , netdev@vger.kernel.org, john.stultz@linaro.org, Richard Cochran , jiri@resnulli.us, ivan.briano@intel.com, henrik@austad.us, jhs@mojatatu.com, levi.pearson@harman.com, intel-wired-lan@lists.osuosl.org, xiyou.wangcong@gmail.com, tglx@linutronix.de, anna-maria@linutronix.de To: Miroslav Lichvar Return-path: Received: from mail-pg0-f44.google.com ([74.125.83.44]:33018 "EHLO mail-pg0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750841AbeARRNi (ORCPT ); Thu, 18 Jan 2018 12:13:38 -0500 Received: by mail-pg0-f44.google.com with SMTP id u1so1358714pgr.0 for ; Thu, 18 Jan 2018 09:13:38 -0800 (PST) Content-Disposition: inline In-Reply-To: <20180118084227.GL1175@localhost> Sender: netdev-owner@vger.kernel.org List-ID: On Thu, Jan 18, 2018 at 09:42:27AM +0100, Miroslav Lichvar wrote: > In the discussion about the v1 patchset, there was a question if the > cmsg should include a clockid_t. Without that, how can an application > prevent the packet from being sent using an incorrect clock, e.g. > the system clock when it expects it to be a PHC, or a different PHC > when the socket is not bound to a specific interface? Right, the clockid_t should be passed in through the CMSG along with the time. Thanks, Richard