From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH v2 0/3] Convert network timestamps to be y2038 safe Date: Tue, 01 Mar 2016 17:19:03 -0500 (EST) Message-ID: <20160301.171903.834892722970175631.davem@davemloft.net> References: <1456561938-7653-1-git-send-email-deepa.kernel@gmail.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, y2038@lists.linaro.org, arnd@arndb.de, vyasevich@gmail.com, nhorman@tuxdriver.com, kuznet@ms2.inr.ac.ru, jmorris@namei.org, yoshfuji@linux-ipv6.org, kaber@trash.net, linux-sctp@vger.kernel.org To: deepa.kernel@gmail.com Return-path: Received: from shards.monkeyblade.net ([149.20.54.216]:42600 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751232AbcCAWTG (ORCPT ); Tue, 1 Mar 2016 17:19:06 -0500 In-Reply-To: <1456561938-7653-1-git-send-email-deepa.kernel@gmail.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Deepa Dinamani Date: Sat, 27 Feb 2016 00:32:14 -0800 > Introduction: > > The series is aimed at transitioning network timestamps to being > y2038 safe. > All patches can be reviewed and merged independently. > > Socket timestamps and ioctl calls will be handled separately. > > Thanks to Arnd Bergmann for discussing solution options with me. > > Solution: > > Data type struct timespec is not y2038 safe. > Replace timespec with struct timespec64 which is y2038 safe. > > Changes v1 -> v2: > Move and rename inet_current_time() as discussed > Squash patches 1 and 2 > Reword commit text for patch 2/3 > Carry over review tags Series applied to net-next, thanks.