From: David Miller <davem@davemloft.net>
To: deepa.kernel@gmail.com
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
Subject: Re: [PATCH v2 0/3] Convert network timestamps to be y2038 safe
Date: Tue, 01 Mar 2016 17:19:03 -0500 (EST) [thread overview]
Message-ID: <20160301.171903.834892722970175631.davem@davemloft.net> (raw)
In-Reply-To: <1456561938-7653-1-git-send-email-deepa.kernel@gmail.com>
From: Deepa Dinamani <deepa.kernel@gmail.com>
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.
prev parent reply other threads:[~2016-03-01 22:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 8:32 [PATCH v2 0/3] Convert network timestamps to be y2038 safe Deepa Dinamani
2016-02-27 8:32 ` [PATCH v2 1/3] net: ipv4: Convert IP " Deepa Dinamani
2016-02-29 4:26 ` YOSHIFUJI Hideaki
2016-02-29 16:31 ` Arnd Bergmann
2016-02-27 8:32 ` [PATCH v2 2/3] net: ipv4: tcp_probe: Replace timespec with timespec64 Deepa Dinamani
2016-02-29 4:27 ` YOSHIFUJI Hideaki
2016-02-27 8:32 ` [PATCH v2 3/3] net: sctp: Convert log timestamps to be y2038 safe Deepa Dinamani
2016-03-01 22:19 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160301.171903.834892722970175631.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=vyasevich@gmail.com \
--cc=y2038@lists.linaro.org \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).