From: Thomas Gleixner <tglx@linutronix.de>
To: Baolin Wang <baolin.wang@linaro.org>
Cc: pang.xunlei@linaro.org, peterz@infradead.org,
benh@kernel.crashing.org, heiko.carstens@de.ibm.com,
paulus@samba.org, jeffv@google.com, cl@linux.com,
mark.d.rustad@intel.com, heenasirwani@gmail.com,
linux-arch@vger.kernel.org, linux-s390@vger.kernel.org,
y2038@lists.linaro.org, mpe@ellerman.id.au,
rafael.j.wysocki@intel.com, ahh@google.com, tiwai@suse.de,
jlayton@primarydata.com, fweisbec@gmail.com, pjt@google.com,
serge@hallyn.com, serge.hallyn@canonical.com, riel@redhat.com,
keescook@chromium.org, arnd@arndb.de, richardcochran@gmail.com,
schwidefsky@de.ibm.com, john.stultz@linaro.org,
james.l.morris@oracle.com, rth@twiddle.net, sds@tycho.nsa.gov,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
pmoore@redhat.com, linux-security-module@vger.kernel.org,
netdev@vger.kernel.org, tj@kernel.org, linux390@de.ibm.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v4 00/25] Convert the posix_clock_operations and k_clock structure to ready for 2038
Date: Tue, 2 Jun 2015 21:20:45 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1506022115240.20347@nanos> (raw)
In-Reply-To: <1433159093-4548-1-git-send-email-baolin.wang@linaro.org>
On Mon, 1 Jun 2015, Baolin Wang wrote:
> This patch series changes the 32-bit time types (timespec/itimerspec) to
> the 64-bit types (timespec64/itimerspec64), since 32-bit time types will
> break in the year 2038.
That's only true for 32bit systems.
All in all the patch series looks rather reasonable now, except for
the subject lines and the changelogs.
The only technical objection I have is the macro conversion magic in
patch #6. This can be done in a less cryptic and more efficient way.
See the comments to the various patches and please apply them to all
of the series.
Thanks,
tglx
_______________________________________________
Y2038 mailing list
Y2038@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/y2038
next prev parent reply other threads:[~2015-06-02 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 11:44 [PATCH v4 00/25] Convert the posix_clock_operations and k_clock structure to ready for 2038 Baolin Wang
2015-06-02 19:19 ` Thomas Gleixner
2015-06-02 19:20 ` Thomas Gleixner [this message]
2015-06-03 2:13 ` Baolin Wang
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=alpine.DEB.2.11.1506022115240.20347@nanos \
--to=tglx@linutronix.de \
--cc=ahh@google.com \
--cc=arnd@arndb.de \
--cc=baolin.wang@linaro.org \
--cc=benh@kernel.crashing.org \
--cc=cl@linux.com \
--cc=fweisbec@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heenasirwani@gmail.com \
--cc=heiko.carstens@de.ibm.com \
--cc=james.l.morris@oracle.com \
--cc=jeffv@google.com \
--cc=jlayton@primarydata.com \
--cc=john.stultz@linaro.org \
--cc=keescook@chromium.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.d.rustad@intel.com \
--cc=mpe@ellerman.id.au \
--cc=netdev@vger.kernel.org \
--cc=pang.xunlei@linaro.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=pmoore@redhat.com \
--cc=rafael.j.wysocki@intel.com \
--cc=richardcochran@gmail.com \
--cc=riel@redhat.com \
--cc=rth@twiddle.net \
--cc=schwidefsky@de.ibm.com \
--cc=sds@tycho.nsa.gov \
--cc=serge.hallyn@canonical.com \
--cc=serge@hallyn.com \
--cc=tiwai@suse.de \
--cc=tj@kernel.org \
--cc=y2038@lists.linaro.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