From mboxrd@z Thu Jan  1 00:00:00 1970
From: Richard Cochran <richardcochran@gmail.com>
Subject: Re: [RFC v2 net-next 01/10] net: Add a new socket option for a
 future transmit time.
Date: Fri, 19 Jan 2018 18:09:15 -0800
Message-ID: <20180120020915.erlylrbsaejf7ufo@localhost>
References: <20180117230621.26074-1-jesus.sanchez-palencia@intel.com>
 <20180117230621.26074-2-jesus.sanchez-palencia@intel.com>
 <CAF=yD-JCN483_e9U7tb_4+2jGyWKfhS0TzooOui+kS4Gh7RSqw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Jesus Sanchez-Palencia <jesus.sanchez-palencia@intel.com>,
        Network Development <netdev@vger.kernel.org>,
        Jamal Hadi Salim <jhs@mojatatu.com>,
        Cong Wang <xiyou.wangcong@gmail.com>,
        =?utf-8?B?SmnFmcOtIFDDrXJrbw==?= <jiri@resnulli.us>,
        vinicius.gomes@intel.com, intel-wired-lan@lists.osuosl.org,
        anna-maria@linutronix.de, henrik@austad.us,
        Thomas Gleixner <tglx@linutronix.de>,
        John Stultz <john.stultz@linaro.org>, andre.guedes@intel.com,
        ivan.briano@intel.com, levi.pearson@harman.com,
        Richard Cochran <rcochran@linutronix.de>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Return-path: <netdev-owner@vger.kernel.org>
Received: from mail-pg0-f68.google.com ([74.125.83.68]:45871 "EHLO
        mail-pg0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1755643AbeATCJS (ORCPT
        <rfc822;netdev@vger.kernel.org>); Fri, 19 Jan 2018 21:09:18 -0500
Received: by mail-pg0-f68.google.com with SMTP id c194so2735739pga.12
        for <netdev@vger.kernel.org>; Fri, 19 Jan 2018 18:09:18 -0800 (PST)
Content-Disposition: inline
In-Reply-To: <CAF=yD-JCN483_e9U7tb_4+2jGyWKfhS0TzooOui+kS4Gh7RSqw@mail.gmail.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

On Fri, Jan 19, 2018 at 04:15:46PM -0500, Willem de Bruijn wrote:
> > +               if (cmsg->cmsg_len != CMSG_LEN(sizeof(ktime_t)))
> > +                       return -EINVAL;
> 
> I don't see any existing reference to ktime_t in include/uapi. Just use a s64?

Agreed.  I didn't see the point of switching to ktime, either.

Thanks,
Richard