[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180120020915.erlylrbsaejf7ufo@localhost>
Date: Fri, 19 Jan 2018 18:09:15 -0800
From: Richard Cochran <richardcochran@...il.com>
To: Willem de Bruijn <willemdebruijn.kernel@...il.com>
Cc: Jesus Sanchez-Palencia <jesus.sanchez-palencia@...el.com>,
Network Development <netdev@...r.kernel.org>,
Jamal Hadi Salim <jhs@...atatu.com>,
Cong Wang <xiyou.wangcong@...il.com>,
Jiří Pírko <jiri@...nulli.us>,
vinicius.gomes@...el.com, intel-wired-lan@...ts.osuosl.org,
anna-maria@...utronix.de, henrik@...tad.us,
Thomas Gleixner <tglx@...utronix.de>,
John Stultz <john.stultz@...aro.org>, andre.guedes@...el.com,
ivan.briano@...el.com, levi.pearson@...man.com,
Richard Cochran <rcochran@...utronix.de>
Subject: Re: [RFC v2 net-next 01/10] net: Add a new socket option for a
future transmit time.
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
Powered by blists - more mailing lists