From mboxrd@z Thu Jan  1 00:00:00 1970
From: Richard Cochran <richardcochran@gmail.com>
Subject: Re: [Intel-wired-lan] [RFC v2 net-next 01/10] net: Add a new socket
 option for a future transmit time.
Date: Thu, 1 Feb 2018 05:16:02 +0100
Message-ID: <20180201041601.qovxelzmsox7opsf@localhost>
References: <20180117230621.26074-1-jesus.sanchez-palencia@intel.com>
 <20180117230621.26074-2-jesus.sanchez-palencia@intel.com>
 <20180118084227.GL1175@localhost>
 <20180118171335.bhyl76wobdffedho@localhost>
 <8e77a23e-d8f8-78ee-f681-0aa689ba3d22@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Miroslav Lichvar <mlichvar@redhat.com>, netdev@vger.kernel.org,
        john.stultz@linaro.org, Richard Cochran <rcochran@linutronix.de>,
        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: Jesus Sanchez-Palencia <jesus.sanchez-palencia@intel.com>
Return-path: <netdev-owner@vger.kernel.org>
Received: from mail-wr0-f194.google.com ([209.85.128.194]:42499 "EHLO
        mail-wr0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751324AbeBAEQG (ORCPT
        <rfc822;netdev@vger.kernel.org>); Wed, 31 Jan 2018 23:16:06 -0500
Received: by mail-wr0-f194.google.com with SMTP id 41so15939706wrc.9
        for <netdev@vger.kernel.org>; Wed, 31 Jan 2018 20:16:06 -0800 (PST)
Content-Disposition: inline
In-Reply-To: <8e77a23e-d8f8-78ee-f681-0aa689ba3d22@intel.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

On Wed, Jan 31, 2018 at 04:49:36PM -0800, Jesus Sanchez-Palencia wrote:
> While implementing this today it crossed my mind that why don't we have the
> clockid_t set per socket (e.g. as an argument to SO_TXTIME) instead of per packet?

Sounds good to me.

Thanks,
Richard